Design assistance for clinical trial protocols

ABSTRACT

Roughly described, a user instantiates protocol elements in a structured clinical trial protocol database and then draws from them in the development of one or more protocol related documents. The system helps the user select tasks to be performed during the study by reference to a historical database of tasks previously associated with similar protocols. The system automatically generates complex content from protocol elements in the database, and can render overlapping sets of protocol elements differently at different locations in the document. The system can automatically provide advisories indicating aspects of the document that still require completion or highlighting other issues that a sponsoring authority deems important for the document type. After all protocol elements are instantiated in the protocol database, it can then be used to drive the operation of most downstream aspects of the study.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.13/872,460 filed Apr. 29, 2013, which is a continuation of U.S.application Ser. No. 10/454,954 filed Jun. 5, 2003, all of which areincorporated herein by reference in their entirety.

REFERENCE TO COMPUTER PROGRAM LISTING AND TABLE APPENDICES

Computer program listings and Table appendices comprising duplicatecopies of a compact disc, named “FSTK-1006-CPLA,” accompanied U.S.application Ser. No. 10/454,954 and are incorporated herein by referencein their entireties. The discs are in IBM-PC/MS-Windows format. Theappendices include the following files:

design.xsd.txt  8K bytes created May 28, 2003 echooser.xsd.txt  6K bytescreated May 28, 2003 POCCore.xslt.txt 27K bytes created May 28, 2003SampleInstance.xml.txt 61K bytes created May 28, 2003SampleMapper.xml.txt 67K bytes created May 28, 2003 schedule.xsd.txt  8Kbytes created May 28, 2003

COPYRIGHT DISCLAIMER

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure as it appears in the U.S. Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND

1. Field of the Invention

The invention relates to the development of clinical trial protocols,and more particularly to computer-assisted methodologies and structuresfor cost-effective, historically informed development of clinical trialprotocols with reduced likelihood of operational uncertainties.

2. Description of Related Art

Clinical trial protocols are designed to produce scientifically soundnew knowledge about the safety, efficacy or specific therapeuticcharacteristics of a new drug or treatment combination. Clinical trialprotocols developed using modern study design principles havewell-understood statistical hypothesis testing and internal validitycharacteristics. Thus, modern clinical studies are designed to deliverthe most supportable scientific knowledge with the smallest number ofstudy subjects. Despite these more efficient study designs, thecomplexity and associated costs of executing new protocols continue toincrease.

The rising complexity of current protocol designs has resulted in adramatic increase in the operational management overhead required toinitiate, execute, and complete a clinical trial successfully withinbudget and time frame. With the increasing number of patients,investigators, locations, and countries involved in a given trial, it isnot surprising that many clinical trials have significant operationalissues that cause substantial cost/time over-runs or outright trialfailures.

A distinction between scientific versus operational issues in clinicaltrials planning and execution is important. A scientific issue arisesdue to the limited state of current knowledge about the trial agent(s)pharmacologic and therapeutic properties in the experimental clinicalsituation. This lack of scientific knowledge is precisely the reason awell-designed clinical trial is required. Scientific issues areethically justified and do not indicate any problem with the clinicaltrial protocol. Operational issues arise because of unforeseendifficulties in executing the trial within the strict parameters orassumptions embedded implicitly or explicitly within the protocoldesign. In this case, the protocol designers may not have been cognizantof the difficulties the field organization or clinical investigators mayhave in operationalizing specific study design components.

Operational deficiencies can be costly to an organization, especially ifthey require an amendment to the protocol during execution of the trial.Even simple amendments have substantial costs, including the internaloverhead of detecting the need for an amendment, costs for creating theamendment, internal approvals costs for releasing the amendment, costsfor disseminating the amendment and the follow-up effort to ensure thatthe amendment has been incorporated into the clinical trials process ata potentially large number of the trial sites. The cost of an amendmentalso includes the opportunity costs due to study completion delays ordata analysis impact due to inconsistent operational behavior at thetrial sites.

Amendments are only the most visible and more costly manifestation of aspectrum of ways in which operational deficiencies can impact anorganization. A large number of operational issues are handled viaformal and informal communications between study project managers andclinical trials sites. Thus the volume of faxes and telephone calls canbe another “cost” which directly affects team productivity and trialsite performance but is not as visible as a trial amendment.

At most large clinical development organizations, concern about protocoldesign quality has spawned the creation of Protocol Review Committees(PRCs). Although specifics vary widely, the role of the PRC is toprovide a centralized resource for the critical examination of aproposed protocol in a “near-final” form. Unlike Institutional ReviewBoards who are concerned about patient safety, risk/benefit and informedconsent, the focus of the PRC is on scientific merit, study validity,and the appropriate use of scarce clinical development resources. ManyPRCs include representatives from clinical operations and a few includeclinical trial sites so that the operational issues that may be embeddedwithin or implied by a proposed trial design can be examined.

Many organizations that have implemented PRCs now require every protocolto be reviewed and approved by the committee prior to its release to theclinical operations team for field deployment. In addition, many PRCmembers state that a review by the committee often results insubstantial changes to the original protocol. Protocol Review Committeesbring together substantial skills and corporate institutionalexperience, representing an enormous investment of highly trainedpersonnel. For the organizations that have committed to this approach,this investment is deemed to be justifiable, given the high stakes andresources committed to the execution and success of each trial.

PRC reviews do seem to have a positive contribution to the operationalquality of reviewed protocols. But the cost of such reviews is large.PRCs generally require highly trained, expensive senior people toperform time-consuming, detailed review of every protocol prior tointernal approval. The man-hours consumed in analyzing a proposedprotocol, discussing the findings at a PRC meeting, presenting thefindings to the protocol author and then repealing the process in alimited manner after the protocol is revised represent a huge hiddencost. As PRC members leave or rotate, the quality and quantity ofprotocols reviewed by the PRC may vary widely. Thus, while PRC reviewsmay be effective, they are neither scalable nor repeatable.

In addition to or instead of forming Protocol Review Committees, manyorganizations have instituted other methods for improving the quality ofthe protocol during its initial creation. Templates, checklists, andpreviously approved protocols ate common materials provided to protocolauthors to assist with the improvement of the quality of their initialprotocol designs. These methods have numerous drawbacks, however, thatsignificantly limit their usefulness. First, most paper-based methodsare static. That is, these methods are not easily updated, disseminated,and then incorporated into the protocol writer's daily routine. Thus, itis often the case that protocols developed with these tools continue tomake the same operational mistakes long after the organization hasupdated the reference materials.

Second, as people leave the organization, the institutional knowledge ofwhat makes a protocol “work” within that organization is lost. If theemployee was a member of the Protocol Review Committee, this toss ofinstitutional knowledge is even more extensive, impacting the entirerange of protocols reviewed by the PRC.

Third, organizational mergers and alliances result in widely disparateapproaches, assumptions, and standard operating procedures for designingprotocols. Operational knowledge unique to one organization or to aspecific therapeutic area tends to remain within the originalorganization or therapeutic area and therefore not benefit the combinedorganization. Hard-earned (and expensive) experience-based knowledgediffusion occurs only if and when people from one organization migrateinto similar positions within the second organization. Of course, thismigration results in the loss of operational knowledge from the originalclinical operations group.

Accordingly, there is an urgent need for a methodology and tools thatwill assist in the design of clinical trial protocols in acost-effective manner, taking advantage of knowledge built into previousprotocols even where the designers of such protocols are no longeravailable. The methodology should assist in avoiding operationaluncertainties early, before a clinical trial begins according to theprotocol.

SUMMARY OF THE INVENTION

The invention involves methods and tools for electronically assisting inthe design of clinical trial protocols. In an embodiment, the inventioncan take advantage of Intelligent Clinical Protocol (iCP) databasemethodologies, in which clinical trial protocol features are representedin a machine readable data structure that then can be used to drive theoperation of most aspects of the study. Roughly described, according tothe invention, a user creates one or more document models which formallydescribe the structure of a corresponding human-readable document thatwill be an ultimate product of the protocol design process. The documentmodel, referred to herein as an Intelligent Clinical Document (iCD)model, can include pre-specified fields, and variable fields that are tobe rendered from data in the iCP database. The document ultimatelycreated is an instance of the iCD model. The designer then uses aprotocol design tool through which he or she designs the protocol,instantiating and drawing from iCP objects as necessary. The protocoldesign tool can render newly entered iCP data into an iCD instancedynamically and consistently in all the places in the document at whichthe data is required. The protocol design tool also can suggest specifictasks that the designer might want to include in the protocol, based ona historical database of tasks that were associated with previousclinical trial protocols. The protocol design tool also canautomatically and dynamically calculate approximate per-patient costs,based on a historical database of the cost of individual tasks that thedesigner has linked into each patient contact event, and canautomatically provide advisories indicating aspects of the document thateither still require completion in order to avoid operationaluncertainties, or must be modified in order to satisfy a set of rulesthat have been established for the current document type.

The iCP database into which the protocol design tool encodes features ofa protocol, is a highly structured, formal model of a clinical protocol.In a preferred embodiment, the iCP database has been designedspecifically to capture issues that tend to cause operationaldifficulties, and may also be designed to capture other issues that thestudy sponsor design group or other controlling organization deemsimportant for other reasons. With properly declaredorganization-specific preferences for characteristics of iCP elements,along with an organizationally-specified iCD model, the process canavoid the omission of specific parameters, and avoid any ambiguities orvagueness in specific parameters, thereby avoiding operationaluncertainties that can adversely impact the progress of the study. In anaspect of the invention, the protocol design tool takes advantage of themodel formality by identifying and reporting, at any time during theprotocol design process, any of a variety of kinds of operationaluncertainties and rule violations for the document type, still presentin the iCP contents or the document being created.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be described with respect to specific embodimentsthereof, and reference will be made to the drawings, in which:

FIG. 1 is an overall functional diagram of an embodiment of a systemaccording to the invention;

FIGS. 2-8 are screen shots of an example for an Intelligent ClinicalProtocol (iCP) database;

FIG. 9 is a flowchart illustrating certain major tacks that might beperformed by a user operating the protocol design tool of FIG. 1;

FIGS. 10, 13, 14, 15, 16, 26, 27, 28 and 44 are mockups of GUI screensproduced by the protocol design tool of FIG. 1;

FIGS. 11, 12 and 17-25 are screen shots of screens produced by Protégé2000, and help illustrate the relationship between a protocol meta-modeland an example individual clinical trial protocol;

FIGS. 29, 30, 31 and 32 are flowchart illustrating methods forimplementing certain advisories according to the invention;

FIG. 33 is a diagram illustrating a hierarchy of specifications andtemplates;

FIG. 34 is a screenshot showing top level sections of eChooser.xsd;

FIG. 35 is a screenshot showing the definitions in the ElementChoosersection of eChooser.xsd;

FIG. 36 is a screenshot showing the structure of each Chooser Entry inthe mapping specification;

FIG. 37 is a screenshot showing the enumeration values available asFTElementTypes;

FIG. 38 is a screenshot showing the enumeration values available as anElementEnum;

FIGS. 39, 40, 41 and 42 are screenshots which together show a section ofan example XML mapping specification conforming to an eChooser.xsdschema;

FIG. 43 is a screenshot illustrating a DocumentElements elementTabsection of a mapping specification;

FIG. 45 is an image of a sample schedule of activities table produced inaccordance with a dynamic template;

FIG. 46 is an image of a sample SOA narrative produced in accordancewith another dynamic template;

FIG. 47 is a Rose model illustrating a Class view of participants in thetwo-level schema; and

FIG. 48 is a schematic view of the two-level schema in action in oneembodiment.

DETAILED DESCRIPTION Intelligent Clinical Protocol

In PCT publication No. WO01/93178A2, incorporated by reference herein,there is described a system which defines, manages and evaluatesclinical trial protocols in an overall end-to-end manner. The systemstarts with the creation of protocol meta-models by a central authority,and ends with the conduct of trials by clinical sites, who then reportback electronically for near-real-time monitoring by the sponsor'sclinical operations team and for analysis by the central authority. Thecentral authority first creates protocol meta-models, one for each ofseveral different disease categories, and makes them available toprotocol designers. The protocol designer chooses the meta-modelappropriate for the relevant disease category, and encodes the clinicaltrial protocol within the selected meta-model. The resulting protocoldatabase is referred to herein as an Intelligent Clinical Protocol(iCP), which is an instance of the protocol meta-model, and the iCP canbe used to drive all downstream problem solvers including a problemsolver that indicates to the clinician at a study site exactly whattasks are to be performed at each patient visit. These tasks can includeboth patient management tasks, such as administering a drug or taking ameasurement, and also data management tasks, such as completing andsubmitting a particular case report form (CRF). The workflow graphembedded in the protocol database advantageously also instructs theproper time for the clinician to obtain informed consent from a patientduring the eligibility screening process, and when to perform futuretasks, such as the acceptable date range for the next patient visit. TheiCP database is a highly structured, formal model that can be used tohelp identify any operational uncertainties and other potential issuescontained in the clinical trial protocol.

In one embodiment, the protocol meta-models are created using ameta-model authoring tool. Protégé 2000 is an example of a tool that canbe used as a meta-model authoring tool. Protégé 2000 is described in anumber of publications including William E. Grosso, et. al., “KnowledgeModeling at the Millennium (The Design and Evolution of Protégé-2000),”SMI Report Number: SMI-1999-0801 (1999), available athttp://smi-web.stanford.edu/pubs/SMI_Abstracts/SMI-1999-0801.html,visited Jan. 1, 2000, incorporated by reference herein. In briefsummary, Protégé 2000 is a tool that helps users build other tools thatare custom-tailored to assist with knowledge-acquisition for expertsystems in specific application areas. It allows a user to define“generic ontologies” for different categories of endeavor, and then todefine “domain-specific ontologies” for the application of the genericontology to more specific situations. In many ways, Protégé 2000 assumesthat the different generic ontologies differ from each other by majorcategories of medical endeavors (such as medical diagnosis versusclinical trials), and the domain-specific ontologies differ from eachother by disease category. In the present embodiment, however, allontologies are within the category of medical endeavor known as clinicaltrials and protocols. The different generic ontologies correspond todifferent meta-models, which differ from each other by disease category.In this sense, the generic ontologies produced by Protégé in the presentembodiment are directed to a much more specific domain than thoseproduced in other applications of Protégé 2000.

Since the meta-models include numerous building blocks as well as manyoptions for patient eligibility criteria, a wide variety of differentkinds of clinical trial protocols, both simple and complex, can bedesigned. These meta-models are provided to clinical trial protocoldesigners who use them to encode individual clinical trial protocols. Inone embodiment the designer can again use Protégé 2000 to encode theprotocol, but in a preferred embodiment the designer uses the protocoldesign tool described herein.

Conceptually, an iCP database is a computerized data structure thatencodes most significant operational aspects of a clinical protocol. Inan embodiment, this includes objectives and outcomes, eligibilitycriteria, administrative parameters, the study schedule including studyvisits and tasks performed during those visits, design parameters,justification for tasks included during the protocol, statisticalelements, and study planned metrics. In the embodiments describedherein, the iCP is an object-oriented database, and can be representedin an XML format. But databases deriving from other database paradigms(such as a relational database) also can be used. The iCP structure canbe readily extended to encompass new concepts, new drugs, and newtesting procedures as required by new drugs and protocols. The iCPdatabase is used by most software modules in the overall system toensure that all protocol parameters, treatment decisions, and testingprocedures are captured, kept consistent, and re-used.

Thus the iCP database provides a comprehensive model of a clinicalprotocol so as to support consistent tools created for problems such asaccrual, patient screening and workflow management. By using acomprehensive model and a unifying standard vocabulary, all tools behaveaccording to the same shared set of protocol specifications.

As used herein, the term “database” does not necessarily imply any unityof structure. For example, two or more separate databases, whenconsidered together, still constitute a “database” as that term is usedherein. The iCP is an example of a structured protocol modelingdatabase. As used herein, a database is “structured” if it containssections (such as fields, objects, files, columns, rows or taggedsections) that are related to each other in accordance with rules thatare expected or enforced by one or more external applications. In thissense a structured database differs from a typical word processingdocument because the word processing document lacks an externallyenforced structure. Most databases are structured.

The iCP data structures can be used by multiple tools to ensure that thetool performs in strict compliance with the clinical protocolrequirements. For example, a patient recruitment simulation tool can usethe eligibility criteria encoded into an iCP data structure, and aworkflow management tool uses the visit-specific task guidelines anddata capture requirements encoded into the iCP data structure. Thebehavior of all such tools will be consistent with the protocol becausethey all use the same iCP database.

The iCP database is used to drive all downstream “problem solvers” suchas electronic CRF generators, and assures that those applications arerevised automatically as the protocol changes. This assures protocolcompliance. The protocol design tool described herein draws on externalknowledge bases to help trial designers, including the suggestion ofindividual tasks that might be appropriate for the particular indicationand trial phase targeted by the current protocol, and including costdata to allow designers to choose less costly but equally effectivetasks where possible. The use of such external knowledge bases helpssave protocol design time and cost, and helps to enable a clinical trialprotocol design process that is more akin to customization than to thecurrent “every trial unique” model.

In order to better understand the structure and content of an iCPembodiment, screen shots of screens produced by the modeling andknowledge acquisition tool Protégé 2000 will be used. As mentioned, thedesigner could use Protégé 2000 to encode the protocol directly, butthis would bypass some of the features and advantages of the presentinvention. FIG. 11 is a screen shot illustrating the overall classstructure in the left-hand pane 1110. Of particular interest to thepresent discussion is the class 1112, called “FastTrackClass,” alsooften referred to herein as the ProtocolElement class), and the classesunder class 1112. ProtocolElement 1112 and those below it represent anexample of a protocol meta-model. This particular meta-model is notspecific to a single disease category.

The right-hand pane 1114 of the screen shot of FIG. 11 sets forth thevarious slots that have been established for a selected one of theclasses in the left-hand pane 1110. In the image of FIG. 11, the“protocol” class 1116, a subclass of ProtocolElement 1112, has beenselected (as indicated by the border). In the right-hand pane 1114,specifically in the window 1118, the individual slots for protocol class1116 are shown. Only some of the slots are pertinent to the presentdiscussion; those not discussed herein are not important for anunderstanding of the invention. It can be seen that several of the slotsin the window 1118 contain “facets” which, for some slots, define alimited set of “values” that can be stored in the particular slot. Forexample, the slot “quickScreenCriterion” 1120 can take on only thespecific values “prostate cancer,” “colorectal cancer,” “breast cancer,”etc.

FIG. 12 is a screen shot of a particular instance of class “protocol” inFIG. 11, specifically a protocol object having identifier CALGB 9840. Itcan be seen that each of the slots defined for protocol class 1116 hasbeen filled in with specific values in the protocol class objectinstance of FIG. 12. Whereas FIG. 11 illustrates an aspect of a clinicaltrial protocol meta-model, FIG. 12 illustrates the top-level object ofan example iCP designated CALGB 9840. For example, it can be seen thatfor the iCP CALGB 9840, the slot “quickScreenCriterion” 1120 (FIG. 11)has been filled in by the protocol designer as “Breast Cancer” (item1210 in FIG. 12), which is one of the available values 1122 for thequickScreenCriterion slot 1120 in FIG. 11. In addition, the protocoldesigner has also filled in “CALGB 9840 Eligibility Criteria”, aninstance of EligibilityCriteriaSet class 1124, for anEligibilityCriteriaSet slot (not shown in FIG. 11) of the protocol classobject. Essentially, therefore, the protocol class object of FIG. 12includes a pointer to another object identifying the “furthereligibility criteria” for iCP CALGB 9840.

As used herein, the “identification” of an item of information does notnecessarily require the direct specification of that item ofinformation. Information can be “identified” in a field by simplyreferring to the actual information through one or more layers ofindirection, or by identifying one or more items of differentinformation which are together sufficient to determine the actual itemof information Similarly, when a data object is said to “describe” anaspect of the protocol, there is no requirement that the entiredescription be self-contained within the data object. For example, partof the description can be physically located elsewhere, and merely beeither explicitly or implicitly associated with the data object.

The iCP of FIG. 11 contains the protocol workflow in the form of patientvisits, management tasks to take place during a visit, and transitionsfrom one visit to another. The right-hand pane 1710 of FIG. 17illustrates the slots available for an object instance of the class“visit” 1128. It can be seen that in addition to a slot 1712 forpossible visit transitions, the Visit class also includes a slot 1714for patient management tasks as well as another slot 1716 for datamanagement tasks. In other words, a clinical trial protocol encoded inan iCP can include instructions to clinical personnel not only forpatient management tasks (such as administer certain medication or takecertain tests), but also data management tasks (such as to completecertain CRFs). The terms “visit” and “protocol event” are usedinterchangeably herein. Both are intended to refer to events called forin a protocol, and neither requires any actual patient contact, whetherremote or in person. The terms also do not refer to what is known as“adverse events”, which are not pre-scheduled.

FIG. 18 illustrates a particular instance of visit class 1128, which isincluded in the CALGB 9840 iCP. As can be seen, it includes a window1810 containing the possible visit transitions, a window 1812 containingthe patient management tasks, and a window 1816 showing the datamanagement tasks for a particular visit referred to as “Arm A treatmentvisit”. The data management tasks and patient management tasks are allinstance of the “PatientManagementTask” class 1130 (FIG. 11), the slotsof which are set forth in the right-hand pane 1910 of FIG. 19. The slotsavailable to a protocol designer in a PatientManagementTask object aremostly text fields. Another iCP embodiment is described below in whichthe study schedule part of the iCP includes taskVisit objects in which atask is associated with one or more Visit objects, and each suchassociation further includes a TaskVisitPurpose attribute whichidentifies a purpose for performing the particular task in theparticular visit. Each such association also identifies an Outcomeobject if the reason is to test efficacy or, in some circumstances,safety.

FIG. 20 illustrates the PatientManagementTask object 1816 (FIG. 18),“Give Arm A Paclitaxel Treatment.” Similarly, FIG. 21 illustrates thePatientManagementTask object 1818, “Submit Form C-116”. The kinds ofdata management tasks which can be included in an iCP according to theclinical trial protocol meta-model include, for example, tasks callingfor clinical personnel to submit a particular form, and a task callingfor clinical personnel to obtain informed consent.

Returning to FIG. 17, the values that a protocol designer places in theslot 1712 of a visit class 1128 object are themselves instances ofVisitToVisitTransition class 2210 (FIG. 22) in the meta-model. Theright-hand pane 2212 shows the slots which are available in an object ofthe VisitToVisitTransition class 2210. As can be seen, it includes aslot 2214 which points to the fast visit object of the transition,another slot 2216 which points to a second visit object of thetransition, and three slots 2218, 2220 and 2222 in which the protocoldesigner provides the minimum, maximum and preferred relative time ofthe transition. FIG. 23 shows the contents of a VisitToVisitTransitionobject 1818 (FIG. 18) in the CALGB 9840 iCP.

In addition to being kept in the form of Visit objects, management taskobjects and VisitToVisitTransition objects, the protocol meta-model alsoallows an iCP to keep the protocol workflow in a graphical ordiagrammatic form as well. In fact, it is the graphical form thatprotocol designers typically use, with intuitive drag-and-drop anddrill-down behaviors, when they encode clinical trial protocols usingProtégé 2000. In the protocol meta-model, a slot 1134 is provided in theProtocol object class 1116 for pointing to an object of theProtocolSchemaDiagram class 1132 (FIG. 11). FIG. 24 shows the slotsavailable for ProtocolSchemaDiagram class 1132. As can be seen, theyinclude a slot 2410 for diagrammatic connectors, and another slot 2412for diagram nodes. The diagram connectors are merely theVisitToVisitTransition objects described previously, and the diagramnodes are merely the Visit objects described previously. FIG. 25illustrates the ProtocolSchemaDiagram object 1214 (FIG. 12) in the CALGB9840 iCP. It can be seen that the entire clinical trial protocol schemais illustrated graphically in pane 2510, and the available components ofthe graph (connector objects 2512 and visit objects 2514) are availablein pane 1516 for dragging to desired locations on the graph.

FIGS. 2-8 are screen shots of another example iCP database, created anddisplayed by Protégé 2000 as an authoring tool. This iCP encodesclinical trial protocol labeled CALGB 49802, and differs from the CALGB9840 iCP in that CALGB 49802 was encoded using a starting meta-modelthat was already specific.to a specific disease area, namely cancer. Itwill be appreciated that in other embodiments, the meta-models can beeven more disease specific, for example meta-models directedspecifically to breast cancer, prostate cancer and so on.

FIG. 2 is a screen shot of the top level of the CALGB 49802 iCPdatabase. The screen shot sets forth all of the text fields of theprotocol, as well as a list 210 of patient inclusion criteria and a list212 of patient exclusion criteria.

FIG. 3 is a screen shot of the Management Diagram class object for theiCP, illustrating the workflow diagram for the clinical trial protocolof FIG. 2. The workflow diagram sets forth the clinical algorithm, thatis, the sequence of steps, decisions and actions that the protocolspecification requires to take place during the course of treating apatient under the particular protocol. The algorithm is maintained assets of tasks organized as a graph 310, illustrated in the left-handpane of the screen shot of FIG. 3. The protocol designer adds stepsand/or decision objects to the graph by selecting the desired type ofobject from the palate 312 in the tight-hand pane of the screen shot ofFIG. 3, and instantiating them at the desired position in the graph 310.Buried beneath each object in the graph 310 are fields which theprotocol designer completes in order to provide the required detailsabout each step, decision or action. The user interface of the Protégé2000 authoring tool allows the designer to drill down below each objectin the graph 310 by double-clicking on the desired object. TheManagement Diagram object for the iCP also specifies a First Step (field344), pointing to Consent & Enroll step 314, and a Last Step (field346), which is blank.

Referring to the graph 310, it can be seen that the workflow diagrambegins with a “Consent & Enroll” object 314. This step, which isdescribed in more detail below, includes sub-steps of obtaining patientinformed consent, evaluating the patient's medical information againstthe eligibility criteria for the subject clinical trial protocol, and ifall such criteria are satisfied, enrolling the patient in the trial.

After consent and enrollment, step 316 is a randomization step. If thepatient is assigned to Arm 1 of the protocol (step 318), then workflowcontinues with the “Begin CALGB 49802 Arm 1” step object 320. In thisArm, in step 322, procedures are performed according Arm 1 of the study,and workflow continues with the “Completed Therapy” step 324. If in step318 the patient was assigned Arm 2, then workflow continues at the“Begin CALGB 49802 Arm 2” step 326. Workflow then continues with step328, in which the procedures of protocol Arm 2 are performed and, whendone, workflow continues at the “Completed Therapy” scenario step 324.

After step 324, workflow for all patients proceeds to condition step“ER+ or PR+” step 330. If a patient is neither estrogen-receptorpositive nor progesterone-receptor positive, then the patient proceedsto a “CALGB 49802 long-term follow-up” sub-guideline object step 332. Ifa patient is either estrogen-receptor positive or progesterone-receptorpositive, then the patient instead proceeds to a “Post-menopausal?”condition_step object 334. If the patient is post-menopausal, then thepatient proceeds to a “Begin Tamoxifen” step 336, and thereafter to thelong-term follow-up sub-guideline 332.

If in step 334, the patient is not post-menopausal, then workflowproceeds to a “Consider Tamoxifen” choice step object 338. In this step,the physician using clinical judgment determines whether the patientshould be given Tamoxifen. If so (choice object 340), then the patientcontinues to the “Begin Tamoxifen” step object 336. If not (choiceobject 342), then workflow proceeds directly to the long-term follow-upsub-guideline object 332. It will be appreciated that the graph 310 isonly one example of a graph that can be created in different embodimentsto describe the same overall protocol schema. It will also beappreciated that the library of object classes 312 could be changed to adifferent library of object classes, while still being oriented toprotocol-directed clinical studies.

FIG. 4 is a screen shot showing the result of “drilling down” on the“Consent & Enroll” step 314 (FIG. 3). As can be seen, FIG. 4 contains asub-graph (which is also considered herein to be a “graph” in its ownright) 410. The Consent & Enroll step 314 also contains certain textfields illustrated in FIG. 4 and not important for an understanding ofthe invention.

As can be seen, graph 410 begins with a “collect pre-study variables 1”step object 410, in which the clinician is instructed to obtain certainpatient medical information that does not require informed consent. Step412 is an “obtain informed consent” step, which includes a datamanagement task instructing the clinician to present the study informedconsent form to the patient and to request the patient's signature. Inanother embodiment, the step 412 might include a sub-graph whichinstructs the clinician to present the informed consent form, and if itis not signed and returned immediately, then to schedule follow-upreminder telephone calls at future dates until the patient returns asigned form or declines to participate.

After informed consent is obtained, the sub-graph 410 continues at stepobject 414, “collect pre-study variable 2”. This step instructs theclinician to obtain certain additional patient medical informationrequired for eligibility determination. If the patient is eligible forthe study and wishes to participate, then the flow continues at stepobject 416, “collect stratification variables”. The flow then continuesat step 418, “obtain registration I.D. and Arm assignment” whicheffectively enrolls the patient in the trial.

FIG. 5 is a detail of the “Collect Stratification Variables” step 416(FIG. 4). As can be seen, it contains a number of text fields, as wellas four items of information that the clinician is to collect about thesubject patient. When the clinical site protocol management softwarereaches this stage in the workflow, it will ask the clinician to obtainthese items of information about the current patient and to record themfor subsequent use in the protocol. The details of the “Collectpre-study variables” 1 and 2 steps 410 and 414 (FIG. 4) are analogous,except of course the specific tasks listed are different.

FIG. 6 is a detail of the “CALGB 49802 Arm 1” sub-guideline 332 (FIG.3). As in FIG. 4, FIG. 6 includes a sub-graph (graph 610) and someadditional information fields 612. The additional information fields 612include, among other things, an indication 614 of the first step 618 inthe graph, and an indication 616 of the last step 620 of the graph.

Referring to graph 610, the arm 1 sub-guideline begins with a “Decadronpre-treatment” step object 618. The process continues at a “Cycle 1; Day1” object 622 followed by a choice object 624 for “Assess fortreatment.” The clinician may make one of several choices during step624 including a step of delaying (choice object 626); a step of callingthe study chairman (choice object 628); a step of aborting the currentpatient (choice object 630); or a step of administering the drug understudy (choice object 632). If the clinician chooses to delay (object626), then the patient continues with a “Reschedule next attempt” step634, followed by another “Decadron pre-treatment” step 618 at a futurevisit. If in step 624 the clinician chooses to call the study chairman(object 628), then workflow proceeds to choose step object 636, in whichthe study chair makes an assessment. The study chair can choose eitherthe delay object 626, the “Give Drug” object 632, or the “Abort” object630.

If either the clinician (in object 624) or the study chair (in object636) chooses to proceed with the “Give Drug” object 632, then workflowproceeds to choice step object 638 at which the clinician assesses thepatient for dose attenuation. In this step, the clinician may choose togive 100% dose (choice object 640) or to give 75% dose (choice object642). In either case, after dosing, the clinician then performs “Day 8Cipro” step object 620. That is, on the 8^(th) day, the patient begins acourse of Ciprofloxacin (an antibiotic).

Without describing the objects in the graph 610 individually, it will beunderstood that many of these objects either are themselves specifictasks, or contain task lists which are associated with the particularstep, visit or decision represented by the object.

FIG. 7 is a detail of the long term follow-up object 332 (FIG. 3). Asmentioned in field 710, the first step in the sub-graph 712 of thisobject is a long term follow-up visit scenario visit object 714. Thatis, the sub-guideline illustrated in graph 712 is executed on each ofthe patient's long-term follow-up visits. As indicated in field 724, thelong term follow-up step 332 (FIG. 3) continues until the patient dies.

Object 716 is a case object which is dependent upon the patient's numberof years post-treatment. If the patient is 1-3 years post-treatment,then the patient proceeds to step object 718, which among other things,schedules the next visit in 3-4 months. If the patient is 4-5 yearspost-treatment, then the patient proceeds to step object 720, whichamong other things, schedules the next patient visit in 6 months. If thepatient is more than 5 years post-treatment, then the patient proceedsto step object 722, which among other things, schedules the next visitin one year. Accordingly, it can be seen that in the sub-guideline 712,different tasks are performed if the patient is less than 3 years outfrom therapy, 4-5 out from therapy, or more than 5 years out fromtherapy. Beneath each of the step objects 718, 720 and 722 areadditional workflow tasks that the clinician is required to perform atthe current visit.

FIG. 8 is an example detail of one of the objects 718, 720 or 722 (FIG.7). It includes a graph 810 which begins with a CALGB 49802 f/u visitsteps” consultation branch object 812, followed by sevenelementary_action objects 814 and 816 a-f (collectively 816). Each ofthe consultation action objects 814 and 816 includes a number ofworkflow tasks not shown in the figures. It can be seen from the namesof the objects, however, that the workflow tasks under object 814 are tobe performed at every follow-up visit, whereas the workflow tasks underobjects 816 are to be performed only annually.

As mentioned, an iCP database can be represented in other formats asidefrom a Protégé 2000 database. Submitted herewith in the CD-ROM appendixis a file SampleInstance.xml.txt which describes yet another iCPdatabase, using XML. A database of this format includes a number ofelement groupings to define a clinical trial protocol, including elementgroupings for administrative information, planned metrics, study design,study population information, clinical trial materials, scheduleinformation, statistical information, and study conduct, among others.Of these, the study design and schedule element groupings are mostpertinent to the present description.

The schema for a study schedule section is defined in the fileschedule.xsd in the CD-ROM appendix. The section includes one or moreStudy Schedule objects defining, among other things, study periods,tasks to be performed during the study, and taskVisit objects. More thanone treatment arm can be represented by including more than one StudySchedule object in this section. Each study period can stand by itselfor can include one or more sub-periods (such as sub-phases within atreatment phase). Sub-periods and (if there are no sub-periods) periods,can include one or more Visit objects. Each Visit object containscertain information about the visit, including reference counts for thevisit object in a document being developed.

In the iCP of SampleInstance.xml.txt, there are five periods defined,referred to as Pretreatment, Treatment, Follow up, Discontinued andWithdrawal From Study. The Follow-up period has two sub-periodsdesignated Monitoring and Final Follow-up, but all the other periodshave no sub-periods. The Pretreatment period contains two Visit objectshaving display names Screening and Baseline. The Treatment periodcontains five Visit objects having display names Visit 1-Visit5. TheMonitoring sub-period contains two Visit objects having display namesMonitoring) and Monitoring2, and the Final Follow-up sub-period containsone Visit object having a display name of Follow-up Visit. TheDiscontinued period has one Visit object having a display name ofDiscontinuation, and the Withdrawal From Study period has one Visitobject with the same display name.

The Tasks subsection of a study schedule section in an iCP instanceaccording to the schedule.xsd schema, defines at least one Task objectthat can be associated with Visit objects. In the iCP ofSampleInstance.xml.txt, there are 10 Task objects defined, with displaynames such as Medical History, Neurological Exam, NIHSS, Modified RankinScale (mRS), Lab profile, Tympanic Temperature, Dosing, Barthel Index,Adverse Event Capture and Brain CT. The Task objects also include otherinformation related to the particular task, such as who is to performthe task, cost information (discussed below), and the number of timesthe Task object is referred to in an associated document beingdeveloped.

The TaskVisits subsection of a study schedule section in an iCP instanceaccording to the schedule.xsd schema, can define one or more TaskVisitobjects. A TaskVisit object associates a task with a visit, and containspointers to both the Task object and the Visit object. It also containszero or more TaskVisitPurpose objects (preferably, a particular documenttype can require that there be at least one TaskVisitPurpose object ineach TaskVisit object), each of which identifies a reason for performingthe particular task in the particular visit. Each TaskVisitPurposeobject can also point to an Outcome object (described below), and insome embodiments a pointer to at least one Outcome object is requiredfor a particular document type if the reason for associating theparticular task with the particular visit as given in theTaskVisitPurpose includes certain predefined reasons, such as efficacyand/or safety.

As examples of TaskVisit objects in the iCP of SampleInstance.xml.txt,there are three associated with object ID=6, which is Visit 4 in theTreatment Period. The three tasks associated in these three respectiveTaskVisit objects are object IDs 66, 7 and 9, which are the Task objectsfor Tympanic Temperature, Dosing, and Adverse Event Capture. Thus theclinical trial protocol as represented in the iCP ofSampleInstance.xml.txt, the tasks of Tympanic Temperature, Dosing, andAdverse Event Capture are to be performed during Visit 4 in theTreatment Period. Each of these three tasks are to be performed in othervisits as well, as indicated by other TaskVisit objects associatingthese Task objects with other Visit objects.

The schema for a study design section is defined in the filedesign.xsd.txt in the CD-ROM appendix. The section includes, among otherthings, subsections for defining primary, secondary and tertiaryobjectives for the study, outcomes (endpoints) for a patient in thestudy, and treatment arms, among other things. The objectives aredefined in Objectives objects which contain a textual description of anobjective, reference counts for the Objective object in a document beingdeveloped, pointers to Outcome objects associated with the objective,and an indication of whether the objective is primary, secondary ortertiary. For example, the iCP of Sampleinstance.xml.txt defines oneobjective, which is which is to “Study effects of high-doseacetaminophen and ibuprofen on body temperature in patients with acuteischaemic stroke, and to study the safety of those treatments”. This isidentified in the Objective object as a primary objective, and isassociated with all four of the outcomes defined for the study.

The possible outcomes for a patient in the study are defined in Outcomeobjects in the outcomes subsection. An Outcome object contains a textualstatement of the outcome, reference counts for the Outcome object in adocument being developed, an Outcome Type attribute (such as typesprimaryEfficacy, secondaryEfficacy, tertiaryEfficacy, safety,pharmacoeconomic and other), pointers to one or more associatedObjective object, and an asMeasuredBy attribute. The asMeasuredByattribute contains one or more Measurement objects, each of which pointsto a TaskVisit object. Preferably, a particular document type requiresthat at least all Outcome objects of a particular type, such as typeprimaryEfficacy, include at least one Measurement object in theasMeasuredBy attribute.

In the iCP of SampleInstancexml.txt there are four Outcome objectsdefined. The first Outcome object is described as “Body temperature at24 hours from start of treatment”, and is of type primaryEfficacy. Thisoutcome is identified as being measured by two TaskVisit objects, namelyTaskVisit object ID=17967174318, which associates the TympanicTemperature task (Task object ID=66) with Visit 1 (Visit object ID=3) inthe Treatment period, and TaskVisit object ID=17967174315, whichassociates the same task with the Baseline Visit object (Visit objectID=2) in the Pretreatment period. Thus according to this exampleprotocol, this outcome will be measured by tympanic temperaturemeasurements taken during the baseline visit in the pretreatment periodand the first visit in the treatment period.

The second, third and fourth Outcome objects in SampleInstance.xml.txtare of types secondaryEfficacy, secondaryEfficacy (again) andtertiaryEfficacy, and are described as “Change in baseline temperatureat 1 and 5 days from start of treatment”, “Time with elevated bodytemperature during the first 24 hours and the first five days” and,“Functional outcome at 1 month”, respectively. The attributes of theseOutcome objects are evident from the file SampleInstance.xml.txt.

The treatment arms subsection of a study design section of an iCPaccording to the file design.xsd.txt defines one or more treatment armobjects, each of which defines such attributes as the planned enrollmentfor the arm, the randomization weight for the arm, the materialsassociated with the arm, and a pointer to a Study Schedule object asdescribed above. One treatment arm can have many schedule objectsassociated with it, and one schedule object can be associated with morethan one arm. The iCP of SampleInstance.xml.txt, as an example, includesone treatment arm identifying one Schedule object described above.

Because of the ability to support domain-independent PSMs, certain iCPembodiments described herein enable automation of the entire trialsprocess from protocol authoring to database lock. For example, an iCPcan be used to create multiple trial management tools, includingelectronic case report forms, data validation logic, trial performancemetrics, patient diaries and document management reports. The iCP datastructures can be used by multiple tools to ensure that the toolperforms in strict compliance with the clinical protocol requirements.For example, an accrual simulation tool can be implemented as adomain-independent PSM. Similarly, an embodiment can also include a PSMthat clinical sites can use to simulate their own accrual in advance ofsigning on to perform a given clinical trial. A single PSM is used tosimulate accrual into a variety of studies, because the patienteligibility criteria are all identified in a predetermined format in theiCP for each study. Another PSM helps clinical sites identify likelypatients for a given clinical trial. Yet another PSM guides cliniciansthrough the visit-specific workflow tasks for each given patient asrequired by the protocol. The behavior of all these tools is guaranteedto be consistent with the protocol even as it evolves and changesbecause they all use the same iCP. The tools can also be incorporatedinto a library that can be re-used for the next relevant trial, thuspermitting knowledge to be transferred across trials rather than beingre-invented each time.

Not all embodiments of the protocol design tool described hereinnecessarily produce a protocol modeling database that includes thespecific details needed to drive all the various kinds of PSMs.Nevertheless, important benefits can be obtained by the formal captureand encoding of even some of the parameters of the protocol in thestructured database. For example, content from the protocol document canbe re-used in the creation of other trial-related documents, such as thefinal study report. The formally captured parameters enforce consistencynot only throughout a single document, but across all documents producedfrom the same iCP database. They also enable rule-based testing ofdocuments for satisfaction of document-type-specific completioncriteria, or satisfaction of other predefined criteria. They alsofacilitate structured retrieval of content from the document set, andsubmission of protocol parameters to other databases such asclinicaltrials.gov.

Intelligent Clinical Document Creation—System Overview

As mentioned, despite the complexity of the overall clinical trialdesign and execution effort, most protocols and related study documentsare written today using only a simple word processor, a handful ofdocument templates or macros, broad regulatory guidance, and, in somecases, an electronic or hardcopy version of a previous or similarprotocol. Paper or electronic documents are passed between personnel inclinical development, clinical operations, biometrics, informationtechnology, regulatory affairs, and marketing. Outside consultants,clinical research organizations, and potential key principleinvestigators may also be included in one or more steps in the protocolcreation cycle. Each group reads, interprets, and extracts theinformation required for their specific responsibilities. As comments,revisions, or amendments occur, each group must evaluate these changesfor any impact or prior work and repeat the read/interpret/extractcycle. Operational considerations are often not considered when featuresare added or removed during review cycles. Many years later, when facedwith combining the entire clinical development program, changes bothwithin and between studies must be accurately evaluated, explained, andincorporated into integrated clinical summary reports and the finalregulatory submission. The difficulty of this task is compounded by thehigh rate of transition among members of clinical development programswith whom the history of changes often rests.

Many operational issues can be identified and corrected early in theprocess by requiring that a protocol be encoded into a structuredprotocol modeling database, but it would be desirable to be able to takeadvantage of the structured nature of such a database in assisting theinitial design of the protocol document as well.

FIG. 1 is an overall functional diagram of an embodiment of a systemthat can perform this function. In this diagram, parallelogramsrepresent databases, circles represent tools or services which act onthe databases, and wavy-bottom rectangles represent persistent ornon-persistent documents. In the present embodiment, some of thedatabases represented by parallelograms are represented on disk as oneor more XML documents.

Referring to FIG. 1, a protocol design tool 110 is the primary interfaceto a user who is designing a protocol instance. The protocol designbuilding blocks available to the user are provided to the protocoldesign tool 110 by an iCP model database 114. These building blocks arebased on regulatory considerations and elements commonly used in allprotocols, as derived from guidelines such as International Committee onHarmonization (ICH), “Structure and Content of Clinical Study Reports,”(E3), recommended for adoption at Step 4 on Nov. 30, 1995, www.ich.org(ICH E3), and ICH, “Guideline for Good Clinical Practice,” (E6, Section6), recommended for adoption at step 4 May 1, 1996 (ICH E6) (bothincorporated by reference herein). Often they are also customizedaccording to the unique requirements of a particular company or studysponsor design group.

The protocol design tool 110 is also responsive to an iCD model database116. The iCD model database 116 is shown in FIG. 1 as being divided intotwo sub-databases: a mapping specification 118 and an iCD template 120.Other iCD model databases 116 can be divided differently, or not all.The iCD model database can also include other information that is notprovided to the protocol design tool 110, or is provided onlyindirectly.

In FIG. 1, the iCD template 120 describes the overall structure of adesired document type, such as a clinical trial protocol document forregulatory approval. It includes, among other things, the overalldocument structure, typographic formats with which data is to bepresented at various locations in the document, and are based onregulatory considerations and elements commonly used in all protocols,as derived from guidelines such as ICH E3 and ICH E6, and if desired caninclude predetermined values for certain protocol elements. The documenttemplate 120 is created during a pre-design configuration step andbecomes an initial iCD instance 130. The mapping specification 118 inthe iCD model 116, among other things, defines the element chooser fromwhich the user chooses elements to view or include in the document beingcreated by the protocol design tool 110. In one embodiment, the elementchooser includes at least those elements defined by ICH E6, section 6(contents of a protocol, according to good clinical practice). Themapping specification 118 also defines which of these elements a sponsordesign group requires in each particular type of document, and the orderand groupings in which they are to appear in the element chooser panefor that document type. The mapping specification 118 also includesfixed value elements configured for the sponsor design group (such asthe name of the sponsor), which the user can instantiate in a documentinstance but cannot edit. All of this information is provided to theprotocol design tool 110.

The protocol design tool 110 allows the user to enter information usinga number of different methods. In one method, the protocol design tool110 provides design guides which allow the user to enter certain basicinformation about the protocol being designed. In another method, theuser is presented with a list of iCP elements in a chooser pane,organized in topic groups, and from which the user can select elementsto browse or insert into the protocol document. As mentioned, the listsof which protocol elements are available for choosing in a particulardocument, and which are required-in a particular document, are providedby the mapping specification 118. Certain choices made by the designercan be assisted by reference to a historical database 920, describedhereinafter. In yet another method, the user is presented with adynamically updated view of the document being created, and canindicate, by pointing and clicking in the document view, the field ordocument sections that the user would like to work on next, just as isdone in a typical word processor program. In addition, the user cannavigate around the document by clicking on a desired heading in ahierarchical document table of contents. For all of the entry methods,whenever the user changes document text or other document features thatdo not implicate iCP elements, the protocol design tool 110 updates theiCD instance 130 with the revisions. Whenever the user updates iCPelements (by adding elements, deleting elements or changing elementvalues), the protocol design tool 110 updates an iCP instance 122 withall the revisions. As mentioned, the iCP instance 122 can at the sametime be used to update and ensure consistency across references toprotocol elements within an evolving document or document collection,and in certain embodiments it can also be used to drive a tool whichgoverns the execution of a clinical trial 124, and to drive otherdownstream problem solvers 126 as well.

The iCP instance database 122 is also used by a document creator tool128 to generate and update the iCD instance 130 that is shown to theuser in the dynamic document creation window of the protocol design tool110. The document creator tool 128 promptly refreshes the dynamicdocument creation window whenever the user commits to a change in anyiCP elements that are referenced in the iCD instance. The iCD instanceis essentially a Microsoft Word document that includes visibleindicators and invisible codes. Visible indicators are used for suchthings as identifying to the user fields in the document that refer todata in the iCP, fields in the document that have yet to be filled in,and whether certain fields are required (as specified in the mappingspecification 118). Invisible codes are used for such things asidentifying to the system the location in the document that correspondsto the location of user behavior in the dynamic document window. Theprotocol design tool 110 includes menu choices by which the user cansave the current iCD instance as a Microsoft Word document on disk, orprint the current iCD instance.

The system of FIG. 1 also includes a protocol advisory service 134. Atany time during or after protocol design, the user can request that aprotocol advisory analysis be executed on the document being created.The protocol advisory service 134 uses a set of predefined rules toidentify ambiguities and omissions of required elements in the iCDinstance being created, and to identify missing links between relatedinformation. In order to accomplish this, the protocol advisory service134 receives information from the iCP instance 122 and the iCD instance130 as they currently exist, and the required elements list from themapping specification 118. The list of advisory rule sets to execute fora particular document type can in some embodiments be provided by themapping specification 118. The protocol advisory service 134 produces alist of advisories indicating for the user further work or data entrythat is required or desirable. The user has the option of correcting theissue that resulted in each advisory or, for certain advisories,entering a justification for why no correction is required.

Overall System Flow

FIG. 9 is a flowchart illustrating certain major tasks that might beperformed by a user operating the protocol design tool 110 (FIG. 1). Itwill be appreciated that many of the steps illustrated in this flowchart(as well as in the other flow charts herein) can be performed inparallel or in a different sequence without affecting the functionsachieved.

Referring to FIG. 9, the protocol designer user first selects anappropriate iCP model 114 from which to design an iCP protocol instance.There may be one or more different available document types that can beprepared using the selected iCP model, but in step 914 it is assumedthat the user chooses the iCP model corresponding to a protocol documentfor submission to the U.S. Food and Drug Administration. Other types ofmodels that might be made available at this stage include protocolmodels for other regulatory authorities in other countries, synopsisdocuments, informed consent forms (ICFs), trial study reports,institutional review board (IRB) letters and investigator study manuals.In step 916 the system instantiates both the iCP instance 122 and theiCD instance 130 (FIG. 1). The document is instantiated using standardtexts, images and pre-specified company values provided by the documenttemplate 120. In step 918, the user then begins entering enters certainbasic contextual information such as the title of the protocol, theversion date and time, and the sponsor name and address, to the extentnot already provided by the template 120.

At this point the user can approach the protocol design task in almostany desired sequence. The protocol design tool 110 allows bothstructured and unstructured entry and does not enforce any specificsequence of work. As mentioned, the user can enter information using oneor more design guide workpanes or workpane shortcut buttons, or caninsert an iCP element from an element chooser presented to the userthrough the GUI, or can navigate to another area of the document to workon via the table of contents pane, or can click within the dynamicdocument creation window to work directly within the document. Theflowchart of FIG. 9 illustrates only one possible sequence. For example,step 918 also includes a substep of entering word processing content.While this step is shown in FIG. 9 once near the beginning of theauthoring process, typically the entering of word processing content isthe great bulk of the designer's work and will occur throughout theprocess before, after and between many of the steps shown in the figure.

The user can also instantiate an iCP element reference at a desiredposition in the document in a number of different ways depending on theelement type. For simple elements, such as the protocol title or thephase of the study, the user can perform various intuitive behaviors invarious embodiments, such as double-clicking on the element in thechooser pane to insert it into a desired position in the document in thedocument window. The user can assign or change the value of a simpleelement through the use of a workpane associated with that element type,invoked through the design guide or shortcut buttons, or by appropriatebehavior relative to either the place where the element appears in thechooser pane or a place where a reference to it has been instantiated inthe document. In all such methods, the protocol design tool 110 makesthe desired change to the element in the iCP instance 122 when the usersignals a commit, and the document creator 128 then refreshes allreferences in the document to the same iCP element. In some embodimentsthe user can assign or change the value of an iCP element by enteringthe modification directly in the document window where the elementreference appears. Even here, however, the system makes the desiredchange first to the element in the iCP instance 122, and then in thedocument at all references to the iCP element.

In some embodiments the chooser pane can include library elements thatthe user can instantiate at desired positions in the document instanceby appropriate behavior. Library elements typically are standard textexcerpts that have been pre-drafted for the user, and instantiation ofsuch an element in the document involves copying the text into thedocument rather than inserting an element reference. If the text of alibrary element were to change, the change would not appear in thedocument instance unless the user re-instantiates the element therein.

In some embodiments the chooser pane can include elements that invoke adynamic template when selected by the user for instantiation in thedocument instance. A dynamic template is a pre-programmed procedure thatautomatically generates complex content from iCP elements, such as alist of all tasks to be performed at any time during the study, andinstantiates the content into the document instance. One dynamictemplate can provide generated content with complex formatting, such asa table format. One dynamic template can generate what appears to betext, by placing element references into the document instance in adesired sequence and inserting text between and around the elementreferences. One dynamic template, when it includes an iCP element in thegenerated content, does so by instantiating a reference to the element,in which case the element as it appears in the document instance will beupdated whenever document creator 128 refreshes the dynamic documentcreation window. One dynamic template, when it includes an iCP elementin the generated content, does so by converting the element's value totext. In this case the element as it appears in the document instancewill not be updated when document creator 128 refreshes the dynamicdocument creation window. One dynamic template, when it inserts thegenerated content into the document instance, marks it (or parts of it)in the document instance as “protected” so that the user is unable toedit it directly in the document window. In this case the dynamictemplate might insert a code into the document instance, associated withthe protected regions of the generated content, such that user selectionof a protected region automatically invokes one or more workpanesappropriate for editing the iCP elements referenced in the protectedregion.

In one embodiment, generated content inserted into the document by adynamic template can be marked with a reference to the dynamic templatesuch that a document refresh operation not only updates the simpleelement references in the document to reflect value changes made to theelement in the iCP, but also re-executes all dynamic templatesreferenced in the document (or at least all those affected by thechanges made in the iCP). As an example, suppose the user desires toinsert into the document instance a list of all tasks to be performed atany time during the study. Such a procedure would collect all taskscurrently instantiated in the iCP and insert them in the documentinstance as a list. In an embodiment supporting dynamic templates thatare executable only from the chooser pane, the dynamic template mightinstantiate a reference in the document instance to each task elementthat exists in the iCP instance 122 at that point in the authoringprocess. This can be cumbersome, however, if for example the usersubsequently deletes a task or instantiates a new task in the iCPinstance. In this case the user would also have to manually re-executethe dynamic template to take account of the deleted or newlyinstantiated tasks. In an embodiment that supports dynamic templatereferences in the document instance, however, the template procedure canbe designed to automatically re-execute on every document refresh, or atleast on document refreshes that resulted from a change that affectedtask objects in the iCP.

Continuing with FIG. 9, in step 922, the user begins selecting tasksthat will be performed within the protocol. Task selection may beinformed by historical database 920 as described in more detail below,and this may be enhanced by establishing the indication (step 910) andthe study phase (step 911) for the protocol before or during step 922.In step 924, each task chosen in step 922 is instantiated in the iCPinstance 122 as an iCP task object. If the user is not finished enteringnew tasks yet (step 926), then he or she returns to step 922 in order tochoose another task for inclusion in the protocol. At any point, moretasks can be added. After all tasks, or at least some number of tasks,have been instantiated into the protocol database, then in step 928, theuser uses the protocol design tool 110 to define an event schedule to beincluded in the protocol. An event can be a study period, a studysubperiod, or a visit. Containment may be defined between periods,subperiods, and visits. The events defined in step 928 are instantiatedinto the iCP instance 122 and, if the iCD instance 130 already containsa reference to an appropriate re-executable dynamic template, then thedocument creator 128 automatically updates the iCD instance 130 to showthe new information. After events have been defined, then in step 930,the user uses the protocol design tool 110 in order to link individualtasks chosen in the step 922, to individual events defined in step 928.A given task may be linked to any number of the events. In response, theprotocol design tool 110 instantiates TaskVisit objects in the iCPinstance 122 linking the desired task objects and desired event objectsat which the tasks are to be performed.

In step 934, the user instantiates a Schedule of Activities (SOA) tableinto the document instance 130 by placing the insertion point at adesired position in the document window and invoking an “SOA Table”dynamic template from the chooser. As described in more detail below,the protocol design tool 110 then collects all the iCP elements requiredfor such a table, including visits, tasks and task-visit associations,formats the information as a table and inserts it with appropriate textas needed at the insertion point. In the present embodiment the SOATable dynamic template converts all iCP element values that it uses intotext so that they will not update automatically on document refresh,protects the entire generated content, and inserts an invisible codethat will invoke an appropriate workpane should the user click in thetable.

In step 936, the user instantiates an SOA narrative into the documentinstance 130 by placing the insertion point at a desired position in thedocument window and invoking an “SOA Narrative” dynamic template fromthe chooser. Again as described in more detail below, the protocoldesign tool 110 then collects all the iCP elements required for such anarrative, sequences them and inserts appropriate text before, after andbetween them, and inserts the resulting content into the documentinstance at the insertion point Importantly, the set of iCP elementsincluded in the content generated by the SOA Narrative dynamic templateoverlaps with the set of iCP elements included in the content generatedby the SOA Table dynamic template. As between any two dynamic templates,the sets of iCP elements included can overlap partially or fully; asused herein, a “full overlap” means the two sets are the same. In thepresent embodiment the SOA Narrative dynamic template instantiates inthe document instance all iCP element values that it uses as iCP elementreferences, so that unlike the content generated by the SOA Tabledynamic template, these element references will update automatically ondocument refresh.

In step 938, the user then proceeds to link other elements from theelement chooser into the document at desired locations, and for manysuch user behaviors, the protocol design tool 110 updates the iCPinstance 122 to reflect the user's action. The document creator 128 thenaccordingly updates the iCD instance 130.

In order to better understand user navigation through the document andthe protocol design task, it will be helpful to illustrate certaingraphical user interface (GUI) features that assist the user. Asmentioned, use of these features is only one way that the user mightproceed. The protocol design tool 110 also provides a guided informationentry mechanism that can be used for part or all of the design.

FIG. 10 is a mockup of a GUI screen produced by the protocol design tool110 for the creation of a sample protocol. It contains a number of panesdescribed as follows. Pane 1012 is a navigation pane which shows thedocument sections. These document sections are provided by the iCDtemplate 120 of the iCD model 116 that was selected in step 914. Byclicking on a section name, the user can navigate to a correspondingsection in the dynamic document creation window. Only document sectionsand subsections currently in use in the document are available in pane1012. The user can delete sections or add new sections through the useof a dialog described below with respect to FIG. 13, although removing asection that according to the mapping specification 118 is required, maygenerate a warning.

Pane 1014 is an element chooser pane, which is a unified list of alltrial elements that the sponsor design group has chosen to expose to theuser. The organization of elements in the chooser pane 1014 iscompletely configurable by the sponsor design group by appropriatedefinition in the mapping specification 118, but typically they areaggregated into logical topic groups and sub-groups. If so configured inthe mapping specification 118, elements listed in the element chooserpane 1014 are available to the designer for insertion anywhere in thedocument being created; multiple instantiations of element references inthe document are linked back to the iCP element itself, therebypromoting consistency of terminology throughout the document.

The chooser elements in pane 1014 can in certain embodiments include anumber of status markings. One such marking might indicate that anelement is in use in the iCP instance 122 but not in the iCD instance130. Another such marking might indicate that the element is requiredfor this document type by the mapping specification 118, but is missingfrom the iCD instance. Yet another such marking might indicate that theelement is referenced in the document, but has not been assigned avalue.

Pane 1016 is the document pane, and is the window within which the iCDinstance 130 is shown. The document pane 1016 is essentially a MicrosoftWord editor having certain additional features. Conventional MS Wordbehaviors can be used to edit any of the pre-specified fixed text in thedocument unless specified by the iCD model 116 as being not editable. Inaddition, special visual markings appear in the document pane 1016 toindicate iCP element references. Such markings visually highlightelements that are required according to the iCD model 116 but have novalue, elements that are not required but have no value, elements thatare required and have a value, and elements that are required and have afixed and not editable value.

Manipulation of document sections can be accomplished in the protocoldesign tool 110 through the use of a “list of document sections”dialogue. A mockup for an embodiment of this dialogue is shown in FIG.13. The dialogue shows a list of available document sections, includinghierarchical subsections, and an indication of which sections arecurrently in use in the document. In one embodiment, the sponsor designgroup can specify in the iCD model 116 that certain sections arerequired, and in that case the dialog of FIG. 13 can also indicate whichsections are required. The user is permitted to use this dialogue to addnew user-defined sections anywhere in hierarchy, to delete sectionsunless they are required by the iCD model 116, to rename sections unlessthey are required by the iCD model 116, and to move sections around tothe extent permitted by the iCD model 116. If the user checks a checkboxof a previously unused section, the protocol design tool 110automatically adds the section to the document. If the user unchecks asection in this dialogue, in the protocol design tool 110 removes thatsection from the document. Removal occurs only after a warning if thedocument section contained element references that are required by theiCD model 116. Unchecking a section in this dialogue does not remove itfrom the list of available sections in this dialogue; the user canre-add the section by re-checking the in-use checkbox. The user can alsoadd a new user-defined document section (not defined in the iCD model116) at any place in hierarchy using this dialogue, and can also deletea document section from the list in this dialogue. Again, if there arerequired elements in a section being deleted, then the user is warnedbefore deletion.

In the element chooser pane 1014, it can be seen that 11 top level topicgroupings (sometimes called element tabs) are shown. FIG. 14 shows thechooser pane 1014 with the “StudyDesign” tab expanded. Other kinds ofelements can be included in the chooser in other embodiments, and/orgrouped differently, since as mentioned, the chooser pane is completelyconfigurable in the mapping specification 118. Each section can bedefined in the mapping specification to exhibit its own behaviors forentering new information into the iCP and for linking elements into thedocument. In addition, elements of the iCP instance 122 may appear inmore than one group or sub-group in the chooser, and they may beorganized differently in the chooser than their organization in the iCPinstance 122.

In the embodiment of FIG. 10, the StudyDesign tab of chooser pane 1014includes sub-topics (not shown) for various kinds of patient outcomes(also sometimes referred to herein as endpoints) that might be referredto in the protocol. The mapping specification 118 specifies that thecontents of these sections (i.e. the elements they represent in the iCPinstance 122) can be edited by the user only through a specifiedworkpane. FIG. 16 is a mockup of such a workpane. In this workpane, theuser can define the different patient outcomes, using names to meetstandard terminology within the company if desired. Each outcome isspecified as being of one of several available types enumerated in themapping specification 118; outcomes of types Primary, Secondary andTertiary Efficacy are in use as shown in FIG. 16. The dialog alsoprovides list of currently defined study objectives, and allows the userto link each outcome to one or more of such objectives by clicking in anassociated check-box. Outcomes entered in the dialog of FIG. 16 willappear in the appropriate subsections in chooser pane 1014 after theuser exits the dialog, and they are then available to be selected andinserted wherever they need to be referenced in the document beingdeveloped. Since all references in the document to a given outcome referback to the same iCP element, consistency of term usage throughout thedocument is promoted since the outcome will always appear by the samename.

The tasks section of the chooser pane 1014 provides one method foraccomplishing step 922 (FIG. 9) of selecting tasks for the iCP 122. Inan aspect of the invention, step 922 takes advantage of a historicaldatabase 920 of clinical trial protocols, providing at least twoadvantages. First, reference to such a database helps the user/designerdouble-check that the procedures that the designer wants to use arecommon for the particular type of study that is being designed. Second,it helps the designer double-check that all relevant tasks have beenincluded. Neither of these criteria are absolutes in the presentembodiment the designer is free to deviate from past history ifappropriate for the particular protocol being designed. But having thedatabase available can help the designer avoid unintentional under- andover-inclusion of tasks.

In addition, it can be appreciated that a major cost component ofclinical trials is negotiated investigator costs. Using clinicalknowledge, results from previous studies and regulatory requirements, aprotocol designer currently has much latitude in selecting the type andfrequency of study measurements. Often the designer does not, however,consider the impact on study complexity and cost implied by theinclusion of a particular task in the study's schedule of activities(SOA). Although cost should never preempt scientific necessity,designers sometimes call for a particular kind of test when a lessexpensive but equally satisfactory test might be available. Also, thereis significant quantitative evidence of procedure inflation—theprogressive accumulation of excessive data collection that ultimatelyprovides no useful additional information in the final regulatorydossier. Accordingly, the database 920 also includes an approximate costbenchmark for the tasks it contains, or many of the tasks it contains,and the protocol design tool 110 allows the designer to take advantageof these cost benchmarks as well. These cost benchmarks might representthe historical median cost of the procedure, for example, and can beuseful in prompting thoughts about the cost implication of choosing aparticular procedure. The cost benchmarks in the database 920 do notnecessarily indicate the actual cost that will be incurred peradministration of the particular procedure, but they can neverthelessprovide a relative guideline.

In an embodiment, therefore, the historical database 920 contains anindustry standard procedure list, such as the InternationalClassification of Diseases, v.9, Clinical Modification (ICD-9-CM),incorporated by reference herein. The list is organized hierarchicallyby major therapeutic area, then by an intermediate level grouping ofclinical indications within a major therapeutic area, and then byindividual clinical indications at the lowest level of the hierarchy.For each clinical indication, the database identifies all the clinicaltrial protocols for the indication and the dates on which they wereauthored (or other associated dates). The database also identifies mostof the individual procedures that were included in each protocol.Finally, the database also includes a sub-database that identifies costbenchmarks for such procedure.

Opening the tasks section in element chooser pane 1014 causes the systemto reference the historical database 920. Instead of offering the entirelist of available procedures, the protocol design tool 110 allows thedesigner to filter the list according to a number of criteria. Forexample, the designer can limit the list to only those tasks that havebeen associated with clinical trial protocols dated within a specifiedtime window, such as during the past 36 months. As another example, thedesigner can limit the list to only those tasks that have beenassociated with clinical trial protocols for one or more specifiedclinical indications and/or study phases (such as the study indicationand phase selected in steps 910 and 911 (FIG. 9)). In an embodiment (notshown) the designer can select desired indications by checking orunchecking items at any level of a hierarchically organized list ofclinical indications presented by the protocol design tool 110, therebyallowing the designer to select indications for filtering purposesindividually, by major therapeutic area, or by intermediate levelgrouping. Alternatively, or additionally, the designer can specifyclinical indications using a text-based search in the database 920.

Once the designer has specified filtering criteria, the protocol designtool 110 suggests to the user the list of tasks from the database 920that satisfy the filter criteria. FIG. 15 is a mockup of a dialogshowing the suggested task list in pane 1510. From this list, the usercan choose desired tasks for inclusion in the new protocol. The list oftasks chosen so far is shown in pane 1512 in FIG. 15. As can be seen,the lists in panes 1510 and 1512 both include the cost benchmark fromthe database 920 for each task. In another embodiment, the costbenchmarks might be shown only in one or the other of such panes. Thedesigner can also create new tasks via a control 1514 in the dialog ofFIG. 15, which are not necessarily represented in database 920.

In an embodiment, tasks in database 920 are not offered to the designerin this dialogue if their association with previous clinical trialprotocols does not meet certain association strength criteria. Forexample, in one embodiment, the association strength criteria mightexclude all tasks that are indicated in the historical database 920 ashaving been associated with no more than some predetermined percentageof previous clinical trial protocols for the same indication and trialphase as the protocol being designed. In another embodiment, theassociation strength criteria might exclude all tasks that are indicatedin database 920 as having been included in no more than a predeterminedpercentage of previous clinical trial protocols that satisfy theuser-specified filtering criteria. In another embodiment, theassociation strength criteria might exclude all but the N most commonlyoccurring tacks (N>0) in previous clinical trial protocols representedin database 920 for the same indication and trial phase as the protocolbeing designed. In yet another embodiment, the association strengthcriteria might exclude all but the N tasks indicated in database 920 ashaving been most frequently included in previous clinical trialprotocols that satisfy the user-specified filtering criteria. Many otherassociation strength criteria, and combinations thereof, can be used invarious embodiments. The protocol design tool 110 might also excludetasks for other reasons, such as for protecting the proprietaryinformation of companies or sponsors of individual protocols in thedatabase 920.

The StudySchedule section of chooser pane 1014 provides associatedshortcuts to two workpanes (not shown), EventSchedule andScheduleOfActivities. The EventSchedule entry provides access to onemethod for accomplishing step 928, defining the event schedule. Asmentioned, events identified in the iCP and iCD are not required toinvolve face-to-face patient visits, and the use of the term “visit”herein is merely a convenience. The term “visit”, is usedinterchangeably herein with the term “event”, and is intended to includeany event that the designer wishes to identify in the protocol.

FIG. 26 is a mockup of a workpane presented by the protocol design tool110 for defining or editing the event schedule. As can be seen, theevent schedule workpane can be used to build a list of events, periodsand optional sub-periods for the protocol workflow. No sub-periods areshown in FIG. 26, but a row 2610 is provided in which they would appear.The work pane functions like a grid, with each box representing anevent. Unlike a grid, selection of a parent will also select itschildren, so in this way it functions like a tree control. Each eventcan be inspected, edited or deleted, and the state of whether itcontains detail text is indicated by an icon. Also indicated is whetherthe event is locked, due to being specified by the iCD model as beingfixed, required and uneditable. Additional icons can be used to indicaterepeating events and error states. Each event has both a full name andan abbreviation. The full name is used in the work pane of FIG. 26, andthe abbreviation is used in the SOA (schedule of activities) table.

The ScheduleOfActivities entry in the StudySchedule section of thechooser pane 1014 provides access to one method for accomplishing step930 (FIG. 9) of linking task objects to event objects. In particular, itprovides access to an SOA workpane such as the mock-up shown in FIG. 27.As can be seen, the work pane is organized to show the SOA in tabularform. Along the horizontal dimension of the table, columns areidentified by their abbreviations. The hierarchically related groupingsof events are shown as well in the horizontal dimension. Along thevertical dimension each of the tasks chosen in step 922 are identified,together with their relative cost indications. By placing check marks atindividual crossings in the table grid, the designer is able toassociate individual ones of the tasks with individual ones of theevents. If the user selects a particular visit (column), then the workpane shows the relative cost per patient for that visit. The work panealso shows in column 2710 the total cost per patient over all visits,resulting from the inclusion of each individual task in the study. Otheruser behaviors will also show the relative cost per patient resultingfrom inclusion of an individual task in a particular visit. The totalrelative cost per patient occasioned by the designer's task-visitassociations is shown as well. As with other data entry work panes inthe present embodiment, changes are not made in the iCP instance 122 orin the iCD instance 130 until the user evidences a commit behavior, suchas clicking on an OK button. The screen shot of FIG. 27 shows a singleSOA for all treatment arms of a study. For a multi-arm study in whichdifferent arms require differing assessments, separate tables such asthat of FIG. 27 are available to the designer.

FIG. 28 is a screen shot mockup of an example SOA cell detail data entrydialog. As can be seen, it includes a field 2810 for entering detailtext, and also includes a region 2812 for entering task-event purposes.The user may enter one or more purposes here, but in one embodiment thesystem requires (either immediately or by a subsequently appliedadvisory rule, described below) that at least one purpose be entered foreach task-visit combination. In an embodiment, the list of availablepurposes includes safety, screening, efficacy, treatment and other. Ifthe user selects other, then the system allows (or in one embodimentrequires) the user to enter a text description of that purpose in field2814. If the user selects efficacy as the purpose, then the systemallows (or in one embodiment requires) the user to identify at least oneoutcome from the list of outcomes that have been defined in the iCPinstance 122. The user can enter an outcome also if the selected purposeis safety. The data items illustrated in FIG. 28 are written intorespective fields of a taskVisit object in the iCP 122 which links thetask to the visit, or into a TaskVisitPurpose object in the iCP0122which links to the TaskVisit object.

Dynamic Templates

As mentioned, the protocol design tool 110 provides dynamic templates(also sometimes called macros or macro procedures) that can automate theinsertion of complex content into the document instance 130. Thegenerated content can contain multiple references to data elements inthe ICP as well as mixed text and footnotes. These procedures exploitthe relationships between protocol data elements to express importantconcepts in the trial's underlying design. For instance, a dynamictemplate could document the fact that a particular outcome was beingdetermined by certain assessments on certain visits.

Two examples of such dynamic templates will now be described. Thesetemplates implement step 934 (FIG. 9) of instantiating an SOA table inthe document instance 130, and step 936 of instantiating an SOAnarrative into the document instance 130.

The following is a pseudocode description of the procedure executed bythe SOA Table insertion dynamic template.

for every schedule object create a Dynamic Template element in thedocument insert two section breaks within the document create an emptytable between the two section breaks create an empty column    for everyperiod in the schedule ordered by period. sequence       create a columncontaining the text in period.displayname       if Iperiod.S0A footnoteexists) create footnote reference       for this period in this cell      if (period.subperiods > 0)       in a new row in the context ofthis column       for each subperiod in period ordered bysubperiod.sequence          create child-column for each subperiodcontaining          the text in subperiod.displayname.          if(subperiod.S0Afootnote exists) create a          footnote reference forthis subperiod in the cell          in the context of this column         for each visit in subperiod ordered by visit.sequence            create child-column containing the            vist.displayname and visit.timewindow             if(visit.SOAfootnote exists) created a             footnote            reference for this visit in the cell          next visit      next subperiod    else       in a new row          in the contextof this column          for each visit in period ordered byvisit.sequence          create column containing the vist.displaynameand          visit.timewindow          if (visit.S0Afootnote exists)created a footnote          reference for this visit in the cell      next visit    next period starting at the last initialized row(containing Visits) create new row in column 1 put “Study Timepoint” foreach visit    put visit.studyTimepoint next visit create a new row inittaskcounter to 1 for each task       create new row       puttask[taskcounter).displayName in first column       if(task[taskcounter).S0Afootnote exists) put a footnote       reference tothis task in the cell          for each visit column             if(exists taskvisit for task[taskcounter] and             visit[column])               put an “x” in the visit column if               (taskvisit.SOAfootnote exists)                   addfootnote reference to this                   taskvisit in                  this cell          next visit column      taskcounter++    next next schedule Insert footnotes below grid inorder of creation

FIG. 45 is an image of a sample SOA table produced in the document inaccordance with the above dynamic template.

The following is a pseudocode description of the procedure executed bythe SOA Narrative insertion dynamic template.

Insert Dynamic Template element in the document.. Insert the followinginto the Dynamic Template element's region... For each Period in theSchedule    Print “Period ” + putElementRef(Period.displayName) + “(Duration is ” +    putElementRef(Period.SOADetail.duration) + “) \n”   Print putElementRef(Period.SOADetail.miscDetail) + “\n”    For eachScheduleltem in Period       if (ScheduleItem isA SubPeriod)         indent          Print “<bullet> Subperiod ” +         putElementRef(ScheduleItem.displayName) +“ (Duration is ” +         putElementRef(SubPeriod.SOADetail.duration) + “)\n”         For each Visit in (SubPeriod)ScheduleItem             indent            Print “<bullet>Visit +            putElementRef(Visit.displayName) + “ ( ” +            putElementRef(Visit.studyDayOrTime) + “} (” +            putElementRef(Visit.permittedTimeWindow) + “) ” +            putElementRef(Visit.SOADetail.miscDetail) + “\n”            indent             For each TaskVisit whereTaskVisit.visitlD = Visit.ID                Get Task where Task.ID =TaskVisit.tasklD                Print <bullet>putElementRef(Task.displayName) +                “Personnel: this taskshould be performed by ” +               putElementRef(TaskVisit.whoPerfoms) + “\n”            Next TaskVisit          Next Visit       else //ScheduleItem is Visit          Print “<bullet>Visit ” +putElementRef(Visit.displayName) +          ( “ +putElementRef(Visit_studyDayOrTime) + “} (” +         putElementRef(Visit.permittedTimeWindow) + “) ” +         putElementRef(Visit.SOADetail.miscDetail) + “\n”         indent          For each TaskVisit where TaskVisit.visitID =Visit.ID            Get Task where Task.ID = TaskVisit.taskIK            Print <bullet> putElementRef(Task.displayName) +            “Personnel: this task should be performed by ” +            putElementRef(TaskVisit.whoPerfams) + “\n”          NextTaskVisit       endif    Next Scheduleltem Next Period

FIG. 46 is an image of a sample SOA narrative produced in the documentin accordance with the above dynamic template.

A number of other dynamic templates can also be defined for insertion ofgenerated content into the document. One additional example is for theinsertion of an Efficacy Assessment Listing, which after some headertext, inserts a bulleted list of all tasks and their detail (ifavailable) and task durations (if specified) used during the study thatare used for efficacy for at least one visit. Order is preserved asspecified in the schedule of activities. The text generated by thisdynamic template is protected from uncontrolled user edits. Thefollowing sets forth rough logic that can be used to implement anEfficacy Assessment Listing dynamic template. In this description, dataelements shown between angle brackets (< >) are instantiated in thedocument as element references rather than text.

-   -   Go through all the instances of <taskVisit>s in the iCPInstance.        For each one, if it has a TaskVisitPurpose element whose        purposeType has a type of “efficacy” then add the taskId and        value of the instanceLabel of the Task object pointed to by the        taskId element of that TaskVisit to the result-list. If it is        already in the result list, do not add it again. By the end,        this will create a list of unique taskIds and their descriptions        in result-list.    -   Order result-list so that it mirrors the order that the tasks        are in the SOA table. Then insert into the document the header        text for the generated content and then a bulleted list of tasks        in the established order, where each is task name is followed by        its task detail of present), and then by its duration (if        present).

Another example dynamic template generates a Safety Assessment Listing,which inserts into the document some header text followed by a bulletedlist of all tasks and their detail (if available) and task durations (ifspecified) used during the study that are used for safety during atleast one visit. The order as specified in the schedule of activities isused. The following sets forth rough logic that can be used to implementan Efficacy Assessment Listing dynamic template. In this description,data elements shown between angle brackets (< >) are instantiated in thedocument as element references rather than text.

-   -   Go through all the instances of <taskVisit>s in the iCPInstance.        For each one, fit has a TaskVisitPurpose element whose        purposeType has a type of “Safety” then add the taskId and value        of the instanceLabel of the Task object pointed to by the taskId        element of that TaskVisit to the result-list. If it is already        in the result-list, do not add it again. This will create a list        of unique taskIds and their descriptions in result-list.    -   Order the result list so that it mirrors the order that the        tasks are in the SOA table. Then insert into the document out        header text for the generated content and then a bulleted list        of tasks in the established order, where each is task name is        followed by its task detail (if present), and then by its        duration (if present).

Another example dynamic template generates an Experimental section whichinserts into the document a list of study objectives and certain detailsrelating to the objectives. The text generated by this dynamic templateis protected from uncontrolled user edits. Rough logic to generate anExperimental section for the document is as follows, in which again,data elements displayed in angle brackets (< >) are instantiated in thedocument as element references rather than text. In addition, anyelement reference that does not have a value it and its associated textis not displayed.

For each Objective in Design.Objectives that has type of Primary do:   Print “The primary objective stated as: ” <Objective.statement> “,will be    established by the following outcome measures: ”       Foreach Outcome in Objective.associatedOutcomes, print      <Outcome.statement> “as measured by”          For eachOutcome.asMeasuredBy (a TaskPurpose) print            TaskPurpose.taskId.displayName “performed on Visits ”            Get all the visits for which there is a TaskPurpose withthis             same Taskld and the same purposeType and print bulleted            list of their displayNames. The visits are displayed in a            sorted order based upon the comparative order of the visit's            grandparent period sequence, visit's parent subperiod            sequence, and visit's sequence; if there is no subperiod in            the ancestral hierarchy, then its comparative value is −1.For each Objective in Design.Objectives that has type of secondary do:<same as above> For each Objective in Design.Objectives that has type oftertiary do: <same as above> The text “Performed on visits:” and “asestablished by the following outcome measures:” is adjusted forplurality of items in its associated list.

Another example dynamic template generates a Study Design section whichinserts into the document certain basic information about the studydesign. The text generated by this Dynamic Template is protected fromuncontrolled user edits. Roughly, the following is inserted into thedocument by this dynamic template (angle bracketed elements areinstantiated as element references rather than text, and all elementreferences are displayed regardless of whether there is associated dataor not):

Study <ProtocolSkeleton.protocolId> is a <ProtocolSkeleton.-isMulticentered>, <Design.methodOfAllocation>, <Design.masking>,<Design.studyConfiguration> <Design.controlType> trial of approximately<Metrics.- plannedEvaluableSubjCount> subjects with <ProtocolSkeleton.-indication>, with a treatment duration of <Metrics.-plannedTreatmentDuration>.

Example content inserted into a document by this dynamic template mightbe:

“Study B1234 is a multicenter, randomized, double-blind, parallel-group,placebo-controlled, trial of approximately 900 subjects withhypertension, with a treatment duration of 40 weeks.”

Once protocol content has been generated and inserted into a document itis desirable that it be kept synchronized with the content of the iCPwhen changes are made to the study design. While some changes areautomatically reflected through the embedded protocol references, thereare some types of changes, such as when new object instances orrelationships are created, that could require additional elementreferences to be generated in the text. The protocol design tool 110 hasa mechanism to ensure that this form of synchronization can beaccomplished automatically. This feature is called Auto Execution of theDynamic Templates.

According to this feature, wherever a Dynamic Template is executed in adocument instance, an XML container element (A Macro Element) is createdthat remembers the location of the generated content. There can bemultiple such areas in the document generated by one or more DynamicTemplates. As text is inserted or removed from the area above agenerated region, the XML plugin and Microsoft Word ensure that theapparent location of the element region in the document always surroundsthe correct content.

The iCP infrastructure is aware of changes made to it by any applicationcomponents and is capable of automatically re-executing all of thedynamic templates used in the document. The protocol design tool 110launches this process whenever the lowest level work pane has beenclosed with an affirmative signifying a commit action. At this point, anumber of changes to the iCP instance 122 may have been accumulated asselections were made and accepted in the stack of possible work panes.As the last work pane in the stack is closed, the changes are nowpropagated into the official or base-level iCP instance and will becomepart of the persistent record. After this request has been fulfilled,the Dynamic Template executor regenerates all the content regions usingthe following algorithm:

Refresh Element Cache from Document For each Dynamic Template Element InCache    Get function type from Element    Get function name fromElement    Get region offsets In Document from Element    Collapseregion to zero length    If functionType is VIM       Run functionName,params, at offset.start    Else if functionType is CSHARP       Load dllwhere functionName exists       Run functionName, params, atoffset.start Next Region Stop document redraw For each ElementReference   Find elementPath in element    Lookup value at elementPath in iCP   If (not value equals currentValue in document)       Copy icpValueinto currentValue in document    End If Next Reference Redraw document

Protocol Advisory Service

At any time during the development of the protocol, the designer caninvoke the protocol advisory service 134 (FIG. 1) in order to identifyelements that have not yet been created, or elements that have beencreated but not yet inserted into the document, or elements that havebeen created but not yet completed, or to look for patterns among dataelements that do not adhere to guidelines or otherwise can causeproblems. In one embodiment, the protocol advisory service evaluates anumber of different rule sets, either sequentially or in parallel, toidentify advisories. These include rules to identify a visit object withno tasks assigned, a task with no purpose assigned, a task that has notyet been assigned to any visit, a study outcome that is not beenassigned to any task (every outcome should include an asMeasuredByattribute that points to at least one TaskVisit object or (in anotherembodiment) at least one TaskVisitPurpose object), and elements that aremissing or unreferenced in the current document instance. In many cases,a single advisory rule can produce many advisory instances whenevaluated; this will occur when a rule is general and targets a class ofelements, and more than one element instance is found that satisfies thecondition being tested. The protocol advisory service 134 produces alist of advisory instances identified, in some embodiments organized byadvisory type. An example of a list of advisory instances is illustratedin the screen shot mock-up of FIG. 44. The designer can refer to thislist and correct the instances identified using any of the data entrymethods described previously. Once corrected, an advisory instance willno longer appear in this list after the designer reruns the protocoladvisory service 134. The designer can close (choose to ignore) anadvisory instance, but only if a justification is entered in a textfield corresponding to the advisory instance. The advisory result listof FIG. 44, for example, includes one advisory 4410 that is listed as“closed”, with a justification set forth in the Comment column

The “visit with no tasks” advisory identifies all visit objects in theiCP instance 122 with which no task objects have yet been associated. Aseparate protocol advisory object is created for each visit in the iCPinstance 122 which satisfies this rule.

The “tasks unassigned to visit” advisory identifies the opposite: taskobjects that the user has created in the iCP instance 122, but whichhave not yet been linked to any visit object. There is no requirementthat every task object in the iCP instance 122 be linked to at least onevisit object, because for example the designer may have created the taskobject only for use in other document types related to the iCP instance122. But an advisory of this sort nevertheless might help the designercorrect an issue that was created unintentionally. In one embodiment,this rule can operate by searching the iCP instance 122 for task objectsthat have no associated taskVisit objects.

The “task without a purpose” advisory identifies all task objects in theiCP instance 122 that have been assigned to a visit, but for which theuser has not identified a reason why that task should be performed inthat visit (FIG. 28). In one embodiment, this rule can operate bysearching the iCP instance 122 for all taskVisit objects in which the“purpose” field is null. Again, a separate protocol advisory object iscreated for each taskVisit instance identified by the rule.

The “outcome without assessment task” advisory identifies outcomes thatthe user has defined in the iCP instance 122, but which have not yetbeen specified as a reason for performing a particular task in aparticular visit. Again, there is no requirement that every definedoutcome be used anywhere, because for example some outcomes defined bythe user and instantiated in the iCP instance 122 might be intended forinclusion only in other document types drawing from the same iCPinstance 122. But an advisory of this sort might help the designercorrect an issue that was created unintentionally. In one embodiment,this rule can operate by searching the iCP instance 122 for outcomeobjects that do not point to any TaskVisit or (in another embodiment)TaskVisitPurpose objects in the “asMeasuredBy” attribute.

Whereas the above four advisory types identify certain kinds ofincompleteness by examining only the iCP instance 122, the “missing orunreferenced protocol elements” advisory examines both the iCP instance122 and the iCD instance 130. This protocol advisory addresses issueswith element handling in a document surrounding the breaking of rulesfor “requiredness” (the requirement that a document instance include atleast one reference to an iCP element of a particular type), referencesin the iCD without values, and iCP values that are unused in the iCD.

The term “incompleteness” here refers to incompleteness of the documentbeing created rather than incompleteness of the iCP database 122. Asmentioned, mapping specification 118 defines, for a given document type,which sections must be included in the final document, and which kindsof data must appear in the document. The iCP instance 122 may wellcontain data objects (or attributes of objects) that never need toappear in a particular kind of output document. Thus this protocoladvisory can often report completeness (find no problem) even whencertain data objects or object attributes (such as those not needed forthe document) in the iCP have not been assigned values. Conversely, thesystem of FIG. 1 does not necessarily instantiate objects in the iCPdatabase 122 until the user instructs the system to do so in the courseof authoring. Thus it is also possible for this protocol advisory toreport incompleteness because the user has not yet made reference in thedocument to certain objects that the mapping specification 118 requiresfor completion of that document type, even though all data objects thathave been instantiated in the iCP have been assigned values. Examples ofelements that might be required by a mapping specification for aclinical trials protocol document type are as follows: an indication andphase, at least one objective, a sponsor, and a definition of evaluablepatients.

The “missing or unreferenced protocol elements” advisory identifies fourcases as follows:

-   -   Case 1: Missing required element reference; no existing values    -   Case 2: Missing required element reference; existing values    -   Case 3: Defined but unreferenced element value, element not        required    -   Case 4: Referenced without value

In one embodiment, the search for advisories in the four cases can occurentirely separately and in sequence. In another embodiment, the searchcan be partially or completely combined. FIG. 29 is a flowchartillustrating a partially combined method. Very simply, as shown in FIG.29, the method involves first calculating four element sets (step 2910),and then using these element sets to calculate the instances satisfyingthe four advisory cases. Cases 1 and 2 are calculated together in step2912, and cases 3 and 4 are calculated thereafter in sequence in steps2916 and 2918, respectively. The four sets calculated in step 2910 areas follows:

-   -   (A) iCP Val: Valued iCP elements. Instances of elements in iCP        instance 122 that have values in the iCP instance. The elements        of this set are identified by searching iCP instance 122 for all        elements of all types, and excluding those with which no value        has been associated (or which have a null value assigned).    -   (B) Required: Elements identified in mapping specification 118        as being “required” in documents of the kind currently being        authored. Only simple elements are included in this set;        elements of type “template” (complex elements that are made up        with other elements) are excluded. The elements of this set are        identified by selecting all chooser elements identified in the        mapping specification 118 for which an ElementType attribute is        not set to “template”, for which a “doctype” attribute is set to        “protocol”, and for which a “required” attribute is set to true.    -   (C) Referenced: all element references in iCD instance 122.    -   (D) Referenced with value: all entries in set C which are bound        to an iCP element that has a value assigned.

Once the above sets have been calculated, the advisory instances forcases 1 and 2 (step 2912) can be calculated as set forth in the flowchart of FIG. 30. First, in step 3010, the service 134 loops through allentries in set B (required elements as defined by mapping specification118). Each such entry identifies an element type. In step 3012, thesystem checks for an element of the specified type in iCD instance 122.If one is found, then the required element exists and the routine loopsto the next entry (step 3012). If not found, then in step 3014 theroutine adds the missing element type to a missing-required list andreturns to looping step 3010. When this loop completes, themissing-required list contains a list of all the element types that areindicated by mapping specification 118 as required in the document, butwhich have not yet been included.

In step 3016, the routine then begins a loop through all element typeson the missing-required list for the purpose of determining which of twokinds of advisories should be used to report each missing element to theuser. Thus in step 3018 the routine determines whether the elementmissing from the document instance has been assigned a value in the iCPinstance 122. This determination is accomplished by determining whetherthe element exists in set A (iCP Val). If not, then in step 3020, theroutine creates a case 1 advisory to inform the user of the element typethat is required but not yet present in the iCD instance 122. Adescriptive user tip is provided as well. If the element does exist atleast once in set A (iCP Val), then some additional assistance can beoffered the user. In particular, in step 3022, the routine creates acase 2 advisory to inform the user of the element type that is requiredbut not yet present in the iCD instance 122, together with the user tip.The case 2 advisory then also lists the current values from set A of allelements of the same type that have values in iCP 122. After theadvisory of case 1 or case 2 has been created, the routine then returnsto looping step 3016 to consider the next element type in themissing-required list. Of course, while the loop 3016 to create case 1and case 2 advisories is combined in the flowchart of FIG. 30, anotherembodiment can identify the case 1 and case 2 advisories in separateloops through the missing-requited element list.

FIG. 31 is a flow chart illustrating how case 3 advisories can beidentified using sets A-D above. Case 3 advisories identify elementsthat have been instantiated in the iCP instance 122 and for which avalue has been assigned, but which have not yet been referenced in thedocument being created. Only elements that are not required by themapping specification 118 are mentioned here. Referring to FIG. 31, instep 3110, the routine loops through all entries in set A (elements iniCP with values). In step 3112, if the current element is present in setC (referenced in the iCP instance 122), then the routine returns tolooping step 3110 and no case 3 advisory is created. If not, then instep 3114, lithe current element is present in set B (elements requiredto be in the document), then again the routine returns to looping step3110 and no case 3 advisory is created. If the element is present inneither of sets C or B, then in step 3116 the routine creates a case 3advisory and returns to looping step 3110. A case 3 advisory merelyidentifies the iCP element and mentions to the user that this elementwas established during protocol design but not referenced in thedocument being created. Note that in another embodiment, an advisorymight be implemented which looks for iCP elements unreferenced in theiCD, whether or not they have assigned values.

FIG. 32 is a flow chart illustrating how advisories for case 4 can becalculated. This advisory identifies elements that are referenced in thedocument, but which are linked to iCP elements that no longer exist(having been deleted by the author in a previous step), or which havebeen linked to an iCP element which has no value assigned. Essentiallythese iCD elements are merely placeholders either that identify anull-valued iCP element, or that point to an iCP element that is notcurrently present in the iCP instance. Placeholders such as these mightarise, for instance, if the document template 120 contained thereference and the configurer intentionally removed the iCP element itpointed to—thus requiring the author to give it a value in the iCP.

Referring to FIG. 32, in step 3210, the routine loops through allentries in set C (iCP element references in the iCD 130). In step 3212,the routine tests whether the current element exists in set A (iCPelements that have assigned values). If so, then the routine returns tolooping step 3210 and no case 4 advisory is created. If not, then a case4 advisory is created in step 3214 and the routine returns to loopingstep 3210. In one embodiment, the case 4 advisory might simply identifyto the user the type of the element contained in the document 130 andstate that it is referenced in the document but has no value. In anotherembodiment, the case 4 advisory might also assist the user with a listof the various values that so far have been assigned to elements of thesame type in the iCP 122.

In one embodiment, advisory rules can be implemented by running rulesagainst the various items in the system of FIG. 1. Each advisory ruleset is implemented as one or more logical assertions about specific dataelements described in three XML documents: the iCP instance 122, themapping specification 118, and the iCD instance 130, as converted to XMLby WorX for Word. WorX for Word is a plug-in to Microsoft Word,available from HyperVision, Ltd., Chicago, Ill., that extends Word tosupport XML and structured authoring bi-directionally.

Assertions take the form of tests that can resolve to a Boolean result.If such a test fails, then this fact is communicated back into theprotocol design tool 110 along with sufficient contextual information toproduce a message which is of help to the user.

Normally, XSL transformation technology is used to produce an outputdocument that is a modification or concatenation of information from itsinput sources. In the present embodiment, however, no document isgenerated. Instead, the system is interested only in the callbacks.

One of the primary advantages of the XSL syntax in this particularmodule of the system is the economy with which one can expressrelatively complex concepts in a declarative way. In addition, havingthis logic external to the application itself means that it can bemodified according to the needs of each study sponsor design groupwithout the need to re-create the release core protocol design tool 110.The economy of expression can be illustrated by the following examplefrom the core of Advisory 1 (visit with no tasks):

<!-- Assert that there is at least 1 TaskViSit associated with thecurrent Visit--> <xsl:when   test=“count($ICP_DOC_ELEM/StudySchedule/Schedule/   TaskVisits/TaskVisit[visit ID/@ID = current( )/@ObjID]) &gt; 0”></xsl:when>

This test returns the count of TaskVisit associations for the currentvisit. If that count is greater than zero, then the rule has passed. Ifthis were to be expressed in a procedural way, then its pseudocode mightlook like this:

Count=0 Foreach TaskVisit in All TaskVisits    If (thisTaskVisit.VisitID= CurrentVisit.ID)       Count = 1       Break    End If End For If(count > 0)    CallError(CurrentVisit)

It can be seen that the XSL syntax simplifies advisory rule setauthoring, maintenance and customization considerably. A number ofadvisories using the XSL syntax are set forth in the filePOCCore.xslt.txt in the CD-ROM appendix.

Many other advisory rules can be implemented in various embodiments, andcalled for by the iCD model 116 for execution with respect to aparticular document type. In one further example, an advisory ruledetects elements that are missing in order for a protocol document to beable to create a valid export according to an external dataspecification, such as the data specification for clinicaltrials.gov orthe data specification for the Protocol Patient Viewer (PPC). In yetanother example, an advisory rule determines what elements are missingin order for protocol document to satisfy ICH E6, section 6. In stillanother further example, an advisory rule checks for the presence in adocument instance of a required complex object, such as an SOA table ornarrative. Such an advisory rule could, for example, check in thedocument for an identification code that the protocol design tool 110inserts into the document in association with the complex object whenthe complex object is generated. In still another further example, anadvisory rule checks for the presence in a document instance of certaindocument sections required for the particular document type.

Yet another advisory rule, referred to herein either as “Outcomesinvolving measurable change” or “Baseline Measures”, advises theprotocol writer when the current protocol has one of the followingproblematic conditions:

-   -   (a) includes an outcome which involves measuring a change, the        protocol indicates a baseline measure for that outcome at a        particular task-visit, but the protocol does not indicate        another later task-visit which is used to measure for that        outcome;    -   (b) a task-visit is noted as a baseline measure, but no        subsequent measure is done (regardless of a linked outcome);    -   (c) an outcome is noted as one that involves measure of change,        a task-visit exists in the protocol to measure for that outcome,        but no corresponding baseline measure is noted at an earlier        task-visit.

To implement this advisory, the model embodiments described above areextended to capture when a measure is a “baseline” measure as well aswhen an outcome is of the type in which a “change” is being measured.Together these two modeling extensions can be used implement the“Outcomes involving measurable change” or “Baseline Measures” advisoryrule.

Advisory rules can be defined also for document templates such as 116.Since a document template in the embodiment of FIG. 1 is merely an iCDinstance 130 that an author has not yet begun working on, advisory rulesapplicable to document templates can be executed by the protocoladvisory service 134 in much the same way that it executes advisoryrules on iCD instances. This general approach and the machinerydescribed can also be used to implement non-regulatory authoringpolicies and conventions of the sponsor design group. By incorporatingthese self-documenting checks directly into the document configuration,the user is relieved of the need to execute an unlinked series ofsponsor-required processes by hand. Typically, this can reduce effortand increase throughput of a sponsor design group as a document ispassed from stakeholder to stakeholder.

Mapping Specification

The mapping specification 118 (FIG. 1) is contained in a set of XMLdocuments. The purpose of the Mapping Specification document, is toprovide the system with configuration information relevant to each ofthe iCP element types that can be collected during document creation.This configuration data is one of the ways that an individualorganization can impress its specific requirements or processes upon thefinished product. For instance, variations in terminology can beresolved wherein the Mapping Specification determines how an entity isto be known in the context of a specific sponsor design group when thesystem's uniform protocol schema is using another name for that entity.Another potentially organization-specific configuration detail specifiesthe “requiredness” or “defaultedness” of each element type in a givendocument type. The Mapping Specification also contains information whichdoes not specifically relate to configuration but is used by the system:for instance, to guide the instantiation of business objects and domainentity linkage. While the Mapping Specification defines each elementtype available in the iCP Schema, some element types can and likely willbe instantiated multiply in an iCP instance, while other element typesdefined in the Mapping Specification will only exist in a one to onerelationship with an iCP instance. Mapping specifications for DomainObjects (as described below) which can be instantiated multiply in theiCP are known as Template specifications.

Before the designer or author begins designing a clinical trial protocolusing the flowchart of FIG. 9, typically the controlling organizationwill prepare the document template 120 by configuring various aspectsbased on the mapping specification 118. This document template can serveas the starting point for the documents of many trial documentinstances, provided that the elements, rules and dynamic templates whichformed the configuration satisfied the requirements of that documenttype. For instance, a Mapping Specification could describe the elementsand document templates that served as a starting point for all Phase IIITrial documents in Oncology, while in another embodiment, a MappingSpecification could serve for all Phase IV Pain Trial documents. Asmentioned, any number of document templates can be created byconfiguration based on a single mapping specification such as 118. Themapping specification itself can be one of several created in accordancewith a common metadata file (XML schema) that defines the elementbuilding blocks that can be used in a mapping specification. Withparticular relevance to the present discussion, a metadata file calledeChooser.xsd defines the elements that can be included in the section ofa mapping specification that defines the elements for element chooserpane 1014 (FIG. 10).

FIG. 33 is a diagram illustrating this hierarchy of specifications andtemplates. As can be seen, the eChooser.xsd metadata file 3310 definesbuilding block elements for the element chooser section of several(three shown) mapping specifications, including mapping specification118 (FIG. 1). Each of the mapping specifications can be used to createmore than one (three shown) document template, including documenttemplate 120, based on mapping specification 118. Finally, as notedabove, each of the document templates can be used to create more thanone document instance, including document instance 130.

Accordingly, in order to understand the element chooser section of themapping specification 118, it will be helpful to review the governingentries in the XML schema file. FIG. 34 is a screenshot showing toplevel sections of eChooser.xsd. It can be seen that among other things,eChooser defines items in the following categories:

-   -   ElementChooser. The root node of the mapping specification. It        serves as the container for the set of concepts represented in        the chooser.    -   ElementTab. A categorization element which produces a        collapsible major tree node in the user interface of the        ElementChooser 1014, which is intended to represent a logical        grouping of protocol elements under a name that is well known to        the user.    -   Element Bucket. Defines a subcategory within an ElementTab, and        is used by the configurer to provide a graphical division        between groups of related elements in a Tab. This graphical        division can be hidden if desired. It is useful if there are no        conceptual subgroups within the protocol elements contained in        an Element Tab.    -   ChooserEntry. Defines the visible and functional attributes of        an entry in the Element Chooser 1014. (As noted above, in single        instance elements—each ChooserEntry corresponds to one entry in        the element chooser workpane 1014. But in the case of multiple        instanced objects, Tasks for example, the ChooserEntry for Task        is a template for all Instances of Task). The Element Chooser        displays both domain objects such as an “Outcome” as well as        atomic protocol elements—simple strings and numbers, which are        the attributes of such objects. Consequently, ChooserEntries are        capable of representing hierarchical or complex objects as well        as the atomic concepts within these. The hierarchical nature of        a ChooserEntry object is expressed in the eChooser schema        representation of the Mapping Specification.    -   FTElementType. Defines the types of elements includable in        documents (“template” (complex) elements and “simple” elements)        and hence the types that will populate the ElementChooser 1014.    -   FTMacroType. Defines the types of Dynamic Templates which the        system can execute.    -   ElementEnum. Defines the set of names corresponding to functions        that are used, to retrieve classes of elements to be used inside        ElementBuckets.    -   WorkPaneTypes. Defines the workpanes that can be referred to by        the chooser.    -   TabColors. Defines tab colors seen in element chooser workpane        1014.

FIG. 35 is a screenshot showing the definitions in the ElementChoosersection of eChooser.xsd. According to this section, a single instance ofan element chooser can be configured to contain zero or more sequencedElementTabs. Each ElementTab can contain zero or more sequencedElementBuckets, an editorClass (workpane to bring up if desired whenuser clicks on it), a tabLabel (display name) to show for that tab, anda tabColor. Each ElementBucket can contain zero or more ChooserEntrys.Each ChooserEntry contains a bucketLabel, an elementType, and a flagthat indicates if the ElementBucket can be hidden if desired.

FIG. 36 is a screenshot showing the structure of each Chooser Entry inthe mapping specification. It contains the following subsections, amongother things:

-   -   ElementStatus: For each specified document type, “required”        indicates whether the element is required to appear at least        once with a value in any document of that type, “default”        indicates whether this element has a fixed read-only value        within a document of that type.    -   “Complex” if the current ChooserEntry includes a sequence of        other ChooserEntry's (sub-entries) then a “Complex” element is        used as the container of its subentries. The sub-entries will        appear in element chooser pane 1014 as a submenu. While it is        permitted to nest ChooserEntries to an arbitrary level of depth,        the user interface enforces practical limits.    -   “tooltip” is a documentation string to be presented on a        mouse-over (or potentially to be used for other purposes)    -   elementPath gives a path identifying the element in the iCP        instance 122. Depending on the whether the Chooser entry defines        a single instance or template element, this path is either        complete (absolute) or a fragment of a path that is composed at        runtime into an absolute canonical path.    -   elementLabel is the display name of the current chooser element,        configurable by the study sponsor design group. For example,        this allows an organization to use the term “endpoint” instead        of “outcome”, if desired. This name is used throughout the        system wherever that element is displayed or input.    -   EditorClass if specified, this field identifies a workpane to        invoke when the user clicks on this entry in the element chooser        pane 1014.    -   detEditorClass if specified, this field identifies a work pane        that is used to edit a single instance of this class of        ChooserEntry when clicked: If both editorClass and        detEditorClass have been defined for a ChooserEntry, then the        detEditorClass value will take precedence.    -   associatedMacro: if specified, this field identifies a macro        (Dynamic Template) that defines how an element of the current        element type should be rendered in the document. The Mapping        Specification contains entries for each of the available macros        (Dynamic Templates) where they are listed in the order required        by the sponsor design group. Typically, they will be displayed        as entries in one or more Tabs (perhaps even in their own Tab).        However, the associatedMacro field is used in the definition of        a Complex element type as an optional way of associating that        element with a specific Dynamic Template. For instance, if there        were a Dynamic Template that emitted a single Visit with its        Tasks, then the “associatedMacro” field of a Visit could be set        to point to that DynamicTemplate. As a general rule, but not        enforced in the system, DynamicTemplates that operate upon a        group of complex protocol objects would be configured to appear        as named procedures on their own, rather than as being silently        associated with each of the displayed instances of a complex        protocol object.    -   enumList: if possible values for this ChooserEntry are defined        in an enumerated set, the set's name is declared in this field.        The set itself is described in another document, not shown.    -   associatedClass:, associatedChooserPath: attributes which are        used in certain ChooserEntries that describe elements which link        to other protocol elements. For example, to describe an        “outcome's” associated “objectives” these attributes help the        system locate the objective being pointed to by any given        instance of an outcome.    -   sectionLevel:, docHeaderStyle: are attributes used in a        ChooserEntry that describes a Document Section ChooserEntry.        These entries are not surfaced in the ElementChooser pane (1014)        but in their own work pane: the DocumentSections work pane.    -   autogenerates: is a Boolean attribute that applies to        ChooserEntries that represent DynamicTemplates. If set, it        indicates that the Template is eligible to be re-run each time        the iCP dataset changes.    -   protected: is a Boolean attribute. When set, it indicates that        when its associated element reference or dynamic template        content is embedded in a document it cannot be edited in the        document itself and must be changed through a work pane.

FIG. 37 is a screenshot showing the enumeration values available asFTElementTypes. These values are defined as follows. Note that aChooserEntry's element type is singular.

-   -   Element: A ChooserEntry which models a discrete data element        such as “study population” or a complex protocol object that can        be instantiated only once    -   Collection: A ChooserEntry which models a collection of like        objects. Typically used as an attribute within a complex object        to designate a collection of pointers to other objects (e.g., an        Outcome's AssociatedObjectives). In this case, the Collection        ChooserEntry is a single element which the system will display        in a submenu as a collection of aliases to the associated        objectives. The concept of alias is discussed below.    -   Template: indicates that the ChooserEntry defines an protocol        object that can be instantiated multiply. This signals the        system that the elementPaths defined for this ChooserEntry and        its sub components are fragments for composition rather than        complete paths    -   Section: indicates that the ChooserEntry is of type        DocumentSection rather than a protocol element.    -   Macro: indicates that the ChooserEntry is a handle to a        DynamicTemplate procedure.    -   CreateNew: is a null ElementType which is used to display a        navigational entry in the ElementChooser (1014) rather than        representing an actual protocol object.    -   FTMacroTypes: VBA, XSLT and CSHARP represent the three platforms        on which DynamicTemplates can be created. The values of this        enumeration help the system locate the procedure to execute.

FIG. 37 also shows the enumeration values available as WorkPaneTypes.Some of the work pane types enumerated here are illustrated inscreenshots of their own in other figures herein.

FIG. 38 is a screenshot showing the enumeration values available as anElementEnum. ElementEnum provides a mapping between element types andfunctions dedicated to retrieving all instances of a class of elementsfrom the iCP for display in the Element Chooser 1014. Thus if theMapping Specification describes an Outcome (a single Templated elementfor the class type: Outcome) the ElementChooserPane will be asked todisplay all instantiated Outcomes. Thus, the value of ElementEnum isused by the protocol design tool 110 to determine which function isneeded to display the list of Outcomes at this position in the ElementChooser Pane 1014.

FIGS. 39, 40, 41 and 42 are screenshots which together show a section ofan example XML, mapping specification 118 conforming to the eChooser.xsdschema 3310. The section shown in these figures includes Administrative,Metrics, StudyDesign element tabs. The StudyDesign tab is expanded toshow three of the included element buckets, called StudyDesign,Objectives, and PrimaryOutcomes. Each of these element buckets isfurther expanded to show a number of chooser entries to be madeavailable as sub-menus under these element buckets. It can be seen thatseveral of the ChooserEntry's shown in these figures include a“required=true” attribute, meaning the document is required to includeat least one element of the type of each of such ChooserEntry. Failureto include at least one of each such element will result in a case 1 orcase 2 missing required element reference advisory. In the “StudyDesign”element bucket, the required elements in this example include (amongothers):

-   -   # study arms (total number of unique study arms in a study);    -   blinding (information regarding blinding of the study);    -   method of subject allocation (the method of assigning treatment        or randomizing a subject to a study arm);    -   study configuration (the configuration of the study (single        group, parallel, etc.));    -   investigational nature (the nature of the investigation of the        study (observational, interventional));    -   overall study outcome (the planned overall outcome of the study        (safety, efficacy, etc.));    -   study purpose (the purpose of the study (treatment, prevention,        etc.)).

The Objectives bucket also includes an “objective” element withattribute “required=true”. The effect of this requires some backgrounddiscussion. As noted elsewhere, a complex element such as Objective canonly be completely rendered by a Dynamic Template. Otherwise, whenreferring to an “Objective” in the context of the system of FIG. 1, oneis normally referring to its alias. The alias for an element type isdefined in the iCP schema and is defaulted into the element's instanceon creation. For example, the alias for an Objective is defined by thecurrent configuration as its “statement” attribute. The alias attributeis known as its InstanceLabel and its value in an Objective is set to“statement”. So simply inserting an Objective in the current document isequivalent to inserting its “statement” attribute. Thus, omission of anObjective's “statement” from the document will cause an advisory to beraised because the “requiredness” setting of a complex element isinherited by the alias by which that object is known in the system.

FIG. 43 is a screenshot illustrating a DocumentElements elementTabsection of the mapping specification 118. This elementTab describes thedocument elements—the sections that can be used in the document—alongwith their heading style, label that should appear, and level ofindentation. In the embodiment of FIG. 43, chooserEntry's do not includethe “required” attribute. In another embodiment, such entries couldinclude the “required” attribute, and the case 1 or case 2 missingrequired element reference advisory (or another protocol advisory) mightbe generated in response to the absence in the document of a documentsection indicated in the mapping specification 118 as “required=true”.

The XML mapping specification 118 also includes a special tab fordynamic templates defined for use with the document. These templateprocedures, when invoked, will insert text and element referencesautomatically into the document, typically at a user-specified position.After placing the document selection cursor at a desired position in thedocument creation window 1016, the user can invoke a Dynamic Template bydouble-clicking the Dynamic Template name in the element chooser pane1014. Dynamic Template elements also can be pre-placed in the documenttemplate by the configurer and will expand dynamically when suitable iCPcontent is inserted. In one implementation, these Dynamic Templates willrender information from the iCP instance 122 into the document.Different Dynamic Templates can be defined to render the sameinformation into the document, each at a respective location specifiedby the user, and each in a different format. For example, one DynamicTemplate might be defined to render the SOA as a table in the document,whereas another Dynamic Template, also available to the user through theelement chooser pane 1014, might be defined to render the SOA in anarrative format. Each chooser entry in the Dynamic Templates sectiondefines how to label the dynamic template in the element chooser pane1014 (display name for the user), what editor should be invoked if theuser clicks on the rendered object in the document, the type of macroimplementation (VBA, XSLT or CSHARP), where to find the macro procedure,and whether the resulting text that is rendered in the document shouldbe protected (read-only).

Another embodiment of an XML mapping specification 118 is submittedherewith in the CD-ROM appendix in file SampleMapper.xml.txt. Thisspecification includes an ElementTab for “Tasks”, having anElementBucket of the same name. In this bucket has only oneChooserEntry, a template-type chooser entry, also called “Tasks”. Thischooser entry refers to an editor workpane like that of FIG. 15, andincludes chooser sub-elements for identifying (among other things) thename of a task, the person responsible for carrying out this task, somedetail about the task, and its duration. The example mappingspecification in SampleMapper.xml.txt also includes an ElementTab for“StudySchedule”, with one ElementBucket called “Schedule”. This elementbucket includes template-type ChooserEntry's for “period”, “subperiod”,“visit”, “taskVisit” and “purpose of task at visit”. Each of thesesub-elements has an associated editor workpane. The “period”template-type chooser entry includes sub-elements for the name oridentifier of a period within the study, additional textual informationpertaining to this period, and the duration of this period in the study,among other things. The “subperiod” template-type chooser entry includessub-elements for similar information. The “visit” template-type chooserentry refers to an editor workpane lice that of FIG. 26, and includesthe following sub-elements, among others: the name or identifier of avisit within the study, the time window in which a visit can take place,the study day or time relative to day 0 for this visit, additionaltextual information pertaining to this visit, and the duration of thisvisit in the study. The “taskVisit” template-type chooser entry refersto an editor workpane like that of FIG. 28, and includes the followingsub-elements, among others: the purpose for this task at this visit, anassociated outcome object, textual detail pertaining to the performanceof this task at this visit, and duration of this task during this visit.The “purpose of task at visit” template-type chooser entry includes thefollowing sub-elements, among others: a pointer to an enumerated purposetype, and a user supplied purpose for this task at this visit.

Two Stage Schema Design

As can be seen, the document architecture model of the system of FIG. 1relies heavily on the concept of references in order to decouple therepresentation of embedded protocol elements from their instances.Isolation of presentation from data is common in the development of userinterfaces, especially in what is conventionally known as “structureddocuments”. But in conventional structured document systems, the data ismade persistent in a backing store (such as in an XML document) and theformatting is maintained in a style-sheet that defines how the variouselements are to be rendered.

The system of FIG. 1, however, has additional requirements that make thetask significantly different than conventional structured documents.First, the document under development is not structured as in a form.While a series of Document Sections may be configured to appear or evenbe required, the internal structure of these sections is notpredetermined and cannot be forced into a constricting schema. Second,structured protocol elements do not “belong” to an instance of adocument, but to the iCP. They are “used” by one or more trial relateddocuments in the written flow of free text or within structuredexpressions that are automatically generated into a document. Thetypographic formatting of these elements is not a characteristic of theelement but of the context in which the element is found.

Third, it is desirable that a user of the system of FIG. 1 be able toalter the position of or even remove the structured element from thedocument without affecting its instance in the backing store.

Fourth, a single element might appear in multiple contexts within thesame document and if there is an underlying change to the element value,it is required that all representations should change text value withminimal change to the extant formatting.

Fifth, it is desired that the user be able to call into existence in thebacking store a previously uninstantiated element and then generate oneor more references to it in the document. Sixth, it is desired that theuser be able to embed a reference to an uninstantiated element into thedocument and instantiate it in the iCP later.

In the system of FIG. 1, these requirements are achieved by providingtwo levels of backing store for a given editing session: a structuredrepository of elements known as the iCP Instance 122 that is sharedbetween all instantiated documents for a given trial, and a repositoryof the evolving document structure known as the iCD instance 130, whichincludes all the free text that adorns the raw iCP data. The iCPinstance 122 contains elements and associations between elements,together constituting the collected domain information about the trial.This is the information which is validated and exported to downstreamapplications. The iCD instance 130 refers to the iCP instance 122through object references managed by dedicated XML “Protocol Reference”nodes in the document. The life cycle of these Protocol Reference nodesis partially decoupled from that of the elements to which they point inthe sense that a value can exist in the iCP without being used in agiven document. Similarly, the document can be made to refer to an iCPelement that does not yet have a value.

Several benefits arise from the two level schema design. In particular,wherever an element is used multiple times in a single document oracross multiple document types, the text values will always be keptsynchronized with each other. Additionally, multiple document types canshare the same data elements. Furthermore, a group of trials can share asimilar core data schema and thus be mined for embedded data relative totrial design while having radically different visual and organizationalcharacteristics as physical documents, and a single set of advisoriescan be used to test the integrity of multiple protocols authored byusers with differing writing styles.

The document schema, or iCD model 116 declares four basic element types:Protocol Reference, Library Reference, Dynamic Template, and DocumentSection. In general, the schema declares that a well formed document canhave mixed free text and any number of each of these elements in anyorder. It further stipulates that Protocol References and LibraryReferences cannot contain other elements or mixed text. Since protocolreferences are used to implement the two stage schema, the presentdiscussion will be limited to these.

The ProtocolReference element is embedded into the subject documentwhenever the document must include text from a corresponding iCPelement. It serves as a link between a physical range in the userdocument 130 and a node somewhere in the iCP instance 122. During anediting session, this link is exercised to refresh the document imagewhen the iCP is changed through the system's workpanes or to refresh thedocument image from the iCP when an iCP element is edited from within aregion in the document pane 1016. Thus a bi-directional update path isrealized by the Reference element in the context of the system. While asubject document is not being edited and is being viewed in aconventional document viewer or printed, the protocol references arerepresented by the text value of their corresponding iCP elements at thetime of last save.

The constituent attributes of a Reference Element are:

-   -   elementPath: Calculated by the system at the time the reference        is created to reflect the canonical path of the iCP element to        which this reference refers.    -   detPanesClass: Copied from the Mapping Specification's        detEditorClass.    -   deleted: Boolean flag set if the iCP element pointed to had a        value a value at one time, but is currently null.    -   unlinked: Boolean flag set if the iCP element has never had a        value.    -   elementLabel: Copied from the Mapping Specification. Indicates        the user's friendly name for this element.    -   default: Boolean, copied from the Mapping Specification to        indicate that the value in this references was supplied at        configuration time.    -   required: Boolean, copied from the Mapping Specification to        indicate that if removed from the document. It may signal a        warning if it is the last instance of this ElementType.    -   wkPaneClass: Copied from the Mapping Specification to indicate        which work pane class should be brought up from a context menu        selection on this object.    -   enumList: Copied from the Mapping Specification. If set, the        name of the constrained set of values that the pointed-to iCP        element can have.

Most of these attributes are copied from the Mapping Specification atthe time the Protocol reference is instantiated in the document. This isan optimization which makes it possible for the system to react quicklyto changes in the document without having to look up the MappingSpecification each time an Element Reference is accessed in thedocument. In another embodiment, the attributes might not be copied fromthe Mapping Specification, but rather simply referred to there whenneeded

While the iCD instance (document) maintains linkage with the iCPinstance, the system uses another mechanism to maintain the dependencybetween documents that rely on a single iCP instance. So for example ifthe name of the sponsor and collaborators were initialized into the iCPduring the writing of a protocol, it is highly likely that theStudyGuide document for the same trial will somewhere use these samedata elements.

In order to centralize the tracking of element usage for each protocolelement, the iCPDocRef element type has been declared in the iCP schema.It allows each protocol element in the iCP instance to contain anassociated set of records indicating which attribute of which protocolelement has been used in which document In this way, warnings can beflagged when an element is no longer used in any document, or when oneis changing the value of an element in the context of one document thatwill affect the contents of another document.

An iCPDocRef element has the following attributes:

-   -   DocType: The name of the Document Type or iCDModel name (e.g.        protocol).    -   RefCount: The number of times the associated iCP        element/attribute has been used in the named document type.    -   ElementPart: The name of the attribute (null if the element        itself) whose reference count is being stored.

The following is an example excerpt from an iCP instance in which threeof the element's attributes are each used once in a document typeentitled “Protocol”:

<sampleSizeCalculation SystemName=“Sample Size Calculation”InstanceLabel=“SystemName” sampleSize=“75” sampleSizeCalcMethod=“”power=“ .80” anticipatedEffectSize= “.5° C” primaryStudyOutcomeID=“1”>   <ICPDocRef DocType=“Protocol” RefCount=    “1”ElementPart=“anticipatedEffectSize”/>    <ICPDocRef DocType=“Protocol”RefCount=    “1” ElementPart=“sampleSize”/>    <ICPDocRefDocType=“Protocol” RefCount=    “1” ElementPart=“power”/></sampleSizeCalculation>

FIG. 47 is a Rose model illustrating the Class view of participants inthe two-level schema in one embodiment. FIG. 48 is a schematic view ofthe two level schema in action in one embodiment.

Summary and Industrial Utility

The relative sizes of budgets would suggest that creating and writing aclinical protocol and associated study documents are trivial costs inthe clinical development process when compared to trial executionexpenses. Yet, growing evidence shows that errors or unnecessarycomplexity in protocol design are often the root cause of poor dataquality and large time and cost impacts in the later steps of drugdevelopment. Thus, any investment in improving protocol design andquality can be an extremely high-leverage opportunity to avoidsubstantial downstream problems—both in the immediate clinical trial andin the much later clinical program's regulatory submission.

Although the content of each protocol differs, the operational featuresof a well-specified protocol are surprisingly similar A robustoperational protocol model can be created without requiring detailedpharmacologic or specific clinical knowledge. Thus, powerfulapplications that apply across all clinical domains can be created toanalyze a protocol's operational features. In addition, by encodingprotocols according to an operational protocol model, institutionalmemory can be captured in a structured, reusable manner. Substantialpersonnel turnover and project reassignments within the clinicaloperations team make it unlikely that a single individual has completeknowledge of the entire development plan for a specific agent. Theoperational protocol model provides a framework for capturing the designfeatures and documenting the justifications for making design decisions.Currently, these justifications are either in people's heads or are partof unwritten company lore. When pressed by regulatory agencies 8-10years later why a study was conducted or modified in a specific manner,either an individual involved in that study must be located or insightinto the decision simply is no longer available. Because the operationaldata model in certain embodiments stores justifications formodifications along with the protocol design, this historicalinformation becomes part of the institutional knowledge base and isaccessible to current and later users.

Operational protocol models and their use with intelligent clinicaldocuments as described herein ensure that quality goals are simplyembedded in the protocol authoring process. Because paper documentsremain the sine qua non for regulatory agencies, generating a completeprotocol document from the operational protocol model is extremelyuseful. And because study designers are used to working with protocoldesign information in the environment and structure of a familiar studydocument rather than in a database, the development of an operationalprotocol model from information entered by a designer relative to thedocument itself is also extremely useful. The protocol authoring systemdescribed herein combines the structured methodology of operationalprotocol models with the familiar environment of standard wordprocessing, thereby enabling familiar but informed protocol design toreplace unstructured protocol writing, while automatically improvingprotocol quality from the very beginning of the protocol life cycle.

As used herein, a given event or value is “responsive” to a predecessorevent or value if the predecessor event or value influenced the givenevent or value. If there is an intervening step or time period, thegiven event or value can still be “responsive” to the predecessor eventor value. If the intervening step combines more than one event or value,the output of the step is considered “responsive” to each of the eventor value inputs. If the given event or value is the same as thepredecessor event or value, this is merely a degenerate case in whichthe given event or value is still considered to be “responsive” to thepredecessor event or value. “Dependency” of a given event or value uponanother event or value is defined similarly.

The foregoing description of preferred embodiments of the presentinvention has been provided for the purposes of illustration anddescription. It is not intended to be exhaustive or to limit theinvention to the precise forms disclosed.

Obviously, many modifications and variations will be apparent topractitioners skilled in this art. As an example, whereas some of theembodiments described herein are implemented using an object-orientedmodel, other embodiments can be implemented using a relational databasemodel. In addition, and without limitation, any and all variationsdescribed, suggested or incorporated by reference in the Backgroundsection of this patent application are specifically incorporated byreference into the description herein of embodiments of the invention.The embodiments described herein were chosen and described in order tobest explain the principles of the invention and its practicalapplication, thereby enabling others skilled in the art to understandthe invention for various embodiments and with various modifications asare suited to the particular use contemplated. It is intended that thescope of the invention be defined by the following claims and theirequivalents.

1. A method of developing a clinical trial protocol for a clinicaltrial, the method comprising: selecting, using a computing device, atleast one task from a historical database that stores a plurality oftasks associated with previous clinical trial protocols; defining, usingthe computing device, an event schedule that comprises at least oneevent in connection with performance of the at least one task; andassociating, using the computing device, in the clinical trial protocolthe at least one task to the at least one event of the event schedule.2. The method of claim 1, wherein selecting the at least one taskcomprises: querying the historical database using a filtering criteria;retrieving a subset of tasks from the plurality of individual tasksbased on the filtering criteria, the subset comprising one or moretasks; and selecting the at least one task from the subset of tasksretrieved.
 3. The method of claim 2, wherein the filtering criteriacomprise at least one of a clinical indication, a trial phase and a pasttime window associated with the previous clinical trial protocols. 4.The method of claim 3, wherein the filtering criteria comprise theclinical indication and a task in the subset of tasks retrieved is for aclinical trial protocol associated with a past protocol date within thepast time window.
 5. The method of claim 3, wherein the filteringcriteria comprise the clinical indication and a task in the subset oftasks has at least a predetermined strength of association to previousclinical trial protocols for the clinical indication.
 6. The method ofclaim 3, wherein, the filtering criteria comprise the trial phase and atask in the subset of tasks has at least a predetermined strength ofassociation to previous clinical trial protocols for the trial phase. 7.The method of claim 2, wherein the filtering criteria comprisestext-based search criteria and a task in the subset of tasks retrievedis for a clinical trial protocol that comprises the text-based searchcriteria.
 8. The method of claim 1, wherein the method further comprisesgenerating a structured protocol modeling database in connection withthe clinical trial protocol.
 9. The method according to claim 1, whereinthe method further comprises scheduling a task of the at least one taskfor performance in at least one event of the clinical trial protocol.10. The method according to claim 1, wherein the method furthercomprises entering a purpose for performing the task scheduled forperformance in the at least one event.
 11. The method according to claim10, wherein entering the purpose comprises selecting the purpose from alist of offered purposes.
 12. The method according to claim 10, whereinthe purpose is one of efficacy, screening, regulatory, safety, andoutcome of the clinical trial.
 13. The method according to claim 10,wherein entering the purpose comprises linking the purpose with atask-event linkage that links a task and an event.
 14. The methodaccording to claim 2, wherein retrieving the subset of tasks includesretrieving a cost estimate for the tasks in the subset.
 15. The methodaccording to claim 14, wherein the cost estimate is retrieved independence upon a historical database that includes task costs.
 16. Themethod according to claim 14, wherein the cost estimate is per purpose.17. The method according to claim 1, wherein the method furthercomprises: generating a table including the at least one event along afirst dimension of the table and the at least one task along a seconddimension of the table; marking at least one task-event linkage in thetable at which the at least one task is linked to the at least oneevent.
 18. The method according to claim 17, wherein the method furthercomprises generating a schedule-of-activities table in dependence uponthe at least one task-event linkage.
 19. The method according to claim18, wherein the method further comprises entering a purpose associatedwith the at least one task-event linkage into the schedule-of-activitiestable.
 20. The method according to claim 17, wherein the method furthercomprises providing, in dependence upon the at least one task-eventlinkage, a total per-patient cost estimate for the clinical trialconducted according to the clinical trial protocol or an event from theat least one event.
 21. The method according to claim 1, wherein themethod further comprises entering an endpoint in connection with apatient in the clinical trial.
 22. The method according to claim 21,wherein the method further comprises associating the endpoint with atleast one measurement in connection with the least one task associatedto the at least one event.
 23. The method according to claim 22, whereinthe endpoint is of a type primary efficacy, secondary efficacy, tertiaryefficacy, safety, or pharmaco-economic.
 24. The method according toclaim 21, wherein entering the endpoint comprises selecting the endpointfrom a list of offered endpoints.
 25. The method according to claim 21,wherein the method further comprises associating the endpoint with anobjective, the objective associated with the clinical trial.
 26. Themethod according to claim 25, wherein the objective is one of primaryobjective, secondary objective, and tertiary objective.
 27. A system todevelop a clinical trial protocol for a clinical trial, the systemcomprising: a computing device comprising a processor and a memorystoring instructions that, when executed by the processor, cause theprocessor to perform operations comprising: selecting at least one taskfrom a historical database that stores a plurality of tasks associatedwith previous clinical trial protocols; defining an event schedule thatcomprises at least one event in connection with performance of the atleast one task; and associating in the clinical trial protocol the atleast one task to the at least one event of the event schedule.
 28. Thesystem of claim 27, wherein the operations of selecting the at least onetask comprise: querying the historical database using a filteringcriteria; retrieving a subset of tasks from the plurality of individualtasks based on the filtering criteria, the subset comprising one or moretasks; and selecting the at least one task from the subset of tasksretrieved.
 29. The system of claim 28, wherein the filtering criteriacomprise at least one of a clinical indication, a trial phase and a pasttime window associated with the previous clinical trial protocols. 30.The system of claim 29, wherein the filtering criteria comprise theclinical indication and a task in the subset of tasks retrieved is for aclinical trial protocol associated with a past protocol date within thepast time window.
 31. The system of claim 29, wherein the filteringcriteria comprise the clinical indication and a task in the subset oftasks has at least a predetermined strength of association to previousclinical trial protocols for the clinical indication.
 32. The system ofclaim 29, wherein, the filtering criteria comprise the trial phase and atask in the subset of tasks has at least a predetermined strength ofassociation to previous clinical trial protocols for the trial phase.33. The system of claim 28, wherein the filtering criteria comprisestext-based search criteria and a task in the subset of tasks retrievedis for a clinical trial protocol that comprises the text-based searchcriteria.
 34. The system of claim 27, wherein the operations furthercomprise generating a structured protocol modeling database inconnection with the clinical trial protocol.
 35. The system according toclaim 27, wherein the operations further comprise scheduling a task ofthe at least one task for performance in at least one event of theclinical trial protocol.
 36. The system according to claim 27, whereinthe operations further comprise entering a purpose for performing thetask scheduled for performance in the at least one event.
 37. The systemaccording to claim 36, wherein the operations of entering the purposecomprise selecting the purpose from a list of offered purposes.
 38. Thesystem according to claim 36, wherein the purpose is one of efficacy,screening, regulatory, safety, and outcome of the clinical trial. 39.The system according to claim 36, wherein the operations of entering thepurpose comprise linking the purpose with a task-event linkage thatlinks a task and an event.
 40. The system according to claim 28, whereinthe operations of retrieving the subset of tasks comprise retrieving acost estimate for the tasks in the subset.
 41. The system according toclaim 40, wherein the cost estimate is retrieved in dependence upon ahistorical database that includes task costs.
 42. The system accordingto claim 40, wherein the cost estimate is per purpose.
 43. The systemaccording to claim 27, wherein the operations further comprise:generating a table including the at least one event along a firstdimension of the table and the at least one task along a seconddimension of the table; and marking at least one task-event linkage inthe table at which the at least one task is linked to the at least oneevent.
 44. The system according to claim 43, wherein the operationsfurther comprise generating a schedule-of-activities table in dependenceupon the at least one task-event linkage.
 45. The system according toclaim 44, wherein the operations further comprise entering a purposeassociated with the at least one task-event linkage into theschedule-of-activities table.
 46. The system according to claim 43,wherein the operations further comprise providing, in dependence uponthe at least one task-event linkage, a total per-patient cost estimatefor the clinical trial conducted according to the clinical trialprotocol or an event from the at least one event.
 47. The systemaccording to claim 27, wherein the operations further comprise enteringan endpoint in connection with a patient in the clinical trial.
 48. Thesystem according to claim 47, wherein the operations further compriseassociating the endpoint with at least one measurement in connectionwith the least one task associated to the at least one event.
 49. Thesystem according to claim 48, wherein the endpoint is of a type primaryefficacy, secondary efficacy, tertiary efficacy, safety, orpharmaco-economic.
 50. The system according to claim 47, wherein theoperations of entering the endpoint comprise selecting the endpoint froma list of offered endpoints.
 51. The system according to claim 47,wherein the operations further comprise associating the endpoint with anobjective, the objective associated with the clinical trial.
 52. Thesystem according to claim 51, wherein the objective is one of primaryobjective, secondary objective, and tertiary objective.